-
Notifications
You must be signed in to change notification settings - Fork 9
Dependencies of produced npm package now contain all required packages #20
Dependencies of produced npm package now contain all required packages #20
Conversation
…s (except for core React modules). Fixes ioBroker#17
# Conflicts: # README.md
@GermanBluefox please merge and release! |
I don't understand, why are modules were removed... |
Lines 26 to 33 in 26c10b9
They are included as dependencies in the package.json of this module (see gulpfile change). Once a dev has included @iobroker/adapter-react , he no longer has to add them to his own package.json, so it shouldn't be mentioned in the README.
|
LGTM |
But it is only valid, if the user uses dev server. And why the gulp file takes and overwrite existing deps? And if I use something else? Maps, image processing? It will be overwritten by gulp task |
I don't understand. You use the gulpfile to release an npm package without The change here only makes it so the released npm package contains the correct dependencies, so this is no longer necessary. |
This has nothing to do with dev-server. It is about using adapter-react with Adapter Creator. The dependencies you create in your package.json (while creating the adapter-react NPM package) are currently empty, thus as @AlCalzone said, every developer needs to add your dependencies as his dependencies. This is wrong. With npm, every package has its own dependencies, and those dependencies need to be mentioned in the package.json of the published npm package. If you look at your published npm package, it has no dependencies at all: https://cdn.jsdelivr.net/npm/@iobroker/adapter-react/package.json |
(except for core React modules)
Tested with the current create-adapter version.
This will fix #17