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

Add acorn to dependency to fix npm Warning #667

Merged
merged 2 commits into from
Jan 4, 2019

Conversation

aliuk2012
Copy link
Contributor

@aliuk2012 aliuk2012 commented Jan 4, 2019

We dont really need it but its needed for Standard and gulp-sourcemaps.

#666 deploy failed because Heroku removes dev dependency by default.

We dont really need it but its needed for Standard and gulp-sourcemaps.

Heroku removes dev dependency by default.
@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-prototype-kit-pr-667 January 4, 2019 12:03 Inactive
@joelanman
Copy link
Contributor

can we add to changelog?

@aliuk2012 aliuk2012 changed the title Move acorn to dependency Add acorn to dependency to fix npm Warning Jan 4, 2019
Copy link
Contributor

@joelanman joelanman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good thanks @aliuk2012 !

@aliuk2012 aliuk2012 merged commit cc3c102 into master Jan 4, 2019
@joelanman joelanman deleted the fix-acorn-dependency-warning branch January 4, 2019 12:56
@joelanman joelanman mentioned this pull request Jan 16, 2019
lfdebrux added a commit that referenced this pull request Dec 14, 2022
In PR #667 we added `acorn` as a direct dependency to fix complaints
from npm about peer dependencies, due to a bug in npm [[1]]. That bug
now appears to have been fixed; removing `acorn` from our `package.json`
does not result in any peer dependency warnings. Also, as we now ensure
that users do not install dev dependencies, we can be confident that
they will not need `acorn`, as it is only required by dev dependencies.

[1]: #666
lfdebrux added a commit that referenced this pull request Dec 14, 2022
In PR #667 we added `acorn` as a direct dependency to fix complaints
from npm about peer dependencies, due to a bug in npm [[1]]. That bug
now appears to have been fixed; removing `acorn` from our `package.json`
does not result in any peer dependency warnings. Also, as we now ensure
that users do not install dev dependencies, we can be confident that
they will not need `acorn`, as it is only required by dev dependencies.

[1]: #666
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.

3 participants