-
-
Notifications
You must be signed in to change notification settings - Fork 871
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
NPM: 6.9.0 AJV Commit causing failure to execute node_modules (multiple dependencies affected i.e. ESLint and WebPack Loaders) #941
Comments
Same error for me #942 here using vue.js |
Is there a workaround to use an earlier release? |
I hope it get noticed fast |
Using nuxt for vue. My solve is doing |
This is certainly related to the latest changes made in the commit history. |
Add
to your package.json will create a work around (I am using yarn, don't know if it will work for npm) |
@epoberezkin can we roll back? |
Can confirm, this is happening for me too when scaffolding Vue JS projects. Currently on Vue CLI 3.4.0, Mac OS 10.13.4. Please fix soon as this is causing serious delays. |
@velocity-360 see my comment, use the work around! 😄 |
Seeing the same thing when using latest
|
@yooouuri thank you however, I am currently contracted to create a Vue tutorial series for a large educational software company and do not think it would be wise to kick off the series with a work-around immediately on the first step. I will wait for resolution. |
@velocity-360 makes sense |
@velocity-360 I'm trying to write a technical test for a job interview in React! 🤣 |
lol @mmacheerpuppy exact same situation for me |
@RickyTony I spent some time debugging and it seems like latest AJV is a dependency for ESLint which may produce a collision. You can use |
workaround for yarn users: "resolutions": {
"ajv": "6.5.5"
} to your package.json and re run |
looks like #941 (comment) beat me to that 😅 |
@mmacheerpuppy I kinda ran out of time for the day debugging, so hopefully it's fixed when I get back to it tomorrow |
this worked for me using npm |
@gregoriB I'm using |
@sky-coding You say that as if we don't have dependency chains on the back-end! @andrewtet can you kindly show your package.json? |
@andrewtet did you run npm install afterwards? |
i think npm users can use this workaround https://github.com/rogeriochaves/npm-force-resolutions |
* See: ajv-validator/ajv#941 * Trying to get fresh build since upgrading lodash * Check for updates on Monday
Hey @epoberezkin we have reported upstream workaround in our linked issue webpack/webpack#8768 so hopefully this reduces the chatter while this is being tackled by your team or other AJV contributors. If there is anything we can do to help, let us know. - webpack team |
Because ajv@6.9.0 does not work with webpack. Ref: ajv-validator/ajv#941
Thanks for the patience, going to fix 7079aed - I think I know what the issue is.
|
released 6.9.1 |
thanks, just test with ajv@6.9.1 and it works now. |
Please let me know if somebody is still affected. The validation of custom keyword was simply incorrect, and now it is fixed. But it is still a bit more restrictive than it was - it would only fail though if e.g. somebody used |
It probably is possible to make travis CI run tests of some dependencies against the new tags (e.g. webpack and eslint). |
@epoberezkin thanks for the fix! |
closing |
Lock the version of AJV for now, until issue is resolved webpack/webpack#8768 ajv-validator/ajv#941
What version of Ajv are you using? Does the issue happen if you use the latest version?
Latest version (6.9.0 release I believe)
Ajv options object
What results did you expect?
Expected to be able to build node_modules but experiencing above stacktrace.
Are you going to resolve the issue?
Current workaround is to remove ESLint dependencies for NPM users, or if using YARN to resolve dependencies to forced version. It's also possible (with the addition of another dependency) to use NPM resolutions (see conversation).
Reproduction
Try using the following packages declaration. npm post install will fail to start. ESLint relies on AJV.
The text was updated successfully, but these errors were encountered: