-
Notifications
You must be signed in to change notification settings - Fork 417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3.1.1 dropping some dependencies. #251
Comments
Further info - the generated master package.json
Can confirm full stops in package names break things - not sure why it wasn't happening in 3.1.0 |
@silver2k Just had a brain flash.... I think I know what it is - The There is a hidden setting for the plugin to increase the buffer size. |
In case this solves your problem, we should increase the default buffer size. Regarding the package name parsing (full stops) I do not remember that there was any change, but I'll check it to be sure. |
See comment above - it's definitely the fullstop in |
@silver2k Thanks for the clarification. Flagged it as bug. |
Found the issue in #246 (commented there). I'll provide a fixed release asap. |
@silver2k Can you try with |
I did a quick check with a test project that includes "stateful.co" and it worked for me with the fix. |
Can confirm it's now working as expected |
Released with 3.1.2 |
This is a Bug Report
Description
As of version 3.1.1 certain dependencies seem to be dropped from packaging. Currently seeing this with
stateful.co
- Not sure if because of full-stop, or something deeper in the package.json.Generated package.json and resulting node-modules folder below (can produce a minimal example - but pressed for time atm):
The text was updated successfully, but these errors were encountered: