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
4.2.0 breaks pre-14.x code #775
Comments
Hi @Cireo, and thanks for reporting! 👍🏻 This is really something I'd like to get to the bottom of. The changes published in v4.2.0 was not meant to break already using projects, but rather allow more project using mustache. There is always a chance we did not consider certain usage scenarios. Before we either update the release notes with migration notes or publish a new version fixing the issue, it's crucial for us to know what exploded on your end. Would you mind sharing any details about your projects? Interesting aspects I can think of;
|
Have not been able to reproduce this kind of error you've reported yet.. Also verified in CI: #779. Still very curious how your project is glued together, so please let us know if you've got a spare moment anytime soon. |
I've tried to reproduce in smaller environments, but wasn't able to. Some extra context
I appreciate you looking into the issue, and will update if I can find a root cause. |
I'm running into a perhaps related problem from eslint-plugin-import:
|
Ahh, my import error is probably related to import-js/eslint-plugin-import#1868. |
Might want to mention this in a release note. Had a nested dependency require
"mustache": "^4.0.1"
which broke something running on earlier npm when 4.1.0 went to 4.2.0The text was updated successfully, but these errors were encountered: