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

Update various dependencies and fix linting offences #885

Merged
merged 14 commits into from
Apr 15, 2020

Conversation

36degrees
Copy link
Contributor

Suggest reviewing commit-by-commit.

@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-prototype-kit-pr-885 April 7, 2020 09:13 Inactive
@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-prototype-kit-pr-885 April 7, 2020 09:14 Inactive
Copy link
Member

@hannalaakso hannalaakso left a comment

Choose a reason for hiding this comment

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

Thanks Ollie 👍

Updating this resolves 2 vulnerabilities in marked as reported by npm audit:

https://npmjs.com/advisories/812
https://npmjs.com/advisories/1076
Acorn is only installed to fix an npm warning, as a dependency of standard and gulp-sourcemap.

The changelog for 7.0.0 suggests that this shouldn't break anything.
ansi-colors is only used in the nodemon task, and this still works fine.
cross-spawn v7.0.0 drops support for Node.js < 8.0.

This is fine as we've required Node ^12.0 in our package.json since November 2019 (a381c8b) and ^10.0 since February 2019 (3803658)
del 4.0.0 drops support for node < 6.0.

del 5.0.0 drops support for node < 8.0, removes the ability to pass in paths with backwards slashes, and updates globby.

None of this affects us.
dotenv 7.0.0 removes a 'load' alias for the config function, which we're not using.

dotenv 8.0.0 drops support for node v6.0.
This is a minor version bump, which wasn't done in 09f5440 because it was previously pinned to a specific version.
Seeing this when running tests:

> Jest did not exit one second after the test run has completed.
>
> This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.

However I'm getting the same output when running tests on master.
The tests still pass!
This is used when creating unique client IDs for usage analytics. I've removed the config and re-generated the client ID and it worked fine.
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