Skip to content
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

move js-yaml to peer dependencies #5

Merged
merged 2 commits into from
Oct 21, 2022
Merged

Conversation

RonaldJerez
Copy link
Contributor

@RonaldJerez RonaldJerez commented Sep 10, 2022

Ensure the right version and instance of js-yaml is used rather than an older hoisted version from projects that are still using the older v3.14 version of js-yaml.

fixes: #2

@ShaMan123
Copy link

ShaMan123 commented Sep 28, 2022

Could be overridden with https://stackoverflow.com/questions/15806152/how-do-i-override-nested-npm-dependency-versions ONLY after it becomes a peer/dep

I am facing the same problem but it isn't solved, seems related to #4

@puzrin puzrin merged commit eeb4f69 into nodeca:master Oct 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

YAMLException: Specified list of YAML types (or a single Type object) contains a non-Type object
3 participants