You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a problem, that some of my project dependencies reference optional dependencies, that I have to disable when doing an npm install by specifying the --no-optional switch (e.g. fsevents on Windows).
The npm install --no-optional works in the SLS project directory, but when doing a serverless webpack, the plugin seems to do a completely separate install of the modules and hangs, because the --no-optional switch was not given to the npm command.
I see two possible solution for that: Either provide some means to add npm options on the command line/config or copy the node modules from the node_modules folder instead of doing it completely separate.
The text was updated successfully, but these errors were encountered:
I created an improvement issue at npm-programmatic for support of arbitrary options on their end. As soon as this has been implemented, the webpack plugin could make use of it and provide the requested feature. Manak/npm-programmatic#9
I have a problem, that some of my project dependencies reference optional dependencies, that I have to disable when doing an
npm install
by specifying the--no-optional
switch (e.g. fsevents on Windows).The
npm install --no-optional
works in the SLS project directory, but when doing aserverless webpack
, the plugin seems to do a completely separate install of the modules and hangs, because the--no-optional
switch was not given to the npm command.I see two possible solution for that: Either provide some means to add npm options on the command line/config or copy the node modules from the node_modules folder instead of doing it completely separate.
The text was updated successfully, but these errors were encountered: