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

Upgrade joi due to deprecation warning #2043

Closed
Pajn opened this issue Apr 24, 2019 · 2 comments · Fixed by #2047
Closed

Upgrade joi due to deprecation warning #2043

Pajn opened this issue Apr 24, 2019 · 2 comments · Fixed by #2047
Assignees

Comments

@Pajn
Copy link

Pajn commented Apr 24, 2019

Library Affected:
workbox-webpack-plugin, workbox-build, probably others.

Browser & Platform:
n/a

Issue or Feature Request Description:
When I install packages today I get:

warning workbox-webpack-plugin > workbox-build > joi@14.3.1: This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning workbox-webpack-plugin > workbox-build > joi > topo@3.0.3: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning workbox-webpack-plugin > workbox-build > joi > hoek@6.1.3: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning workbox-webpack-plugin > workbox-build > joi > topo > hoek@6.1.3: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.

When reporting bugs, please include relevant JavaScript Console logs and links to public URLs at which the issue could be reproduced.

@philipwalton
Copy link
Member

Thanks, @jeffposnick when you're back can you take a look and make sure workbox-build is compatible with the new version?

@jeffposnick
Copy link
Contributor

Unfortunately, I can't find any release notes for v15, so I'm going to assume it was mainly a breaking semver change due to the renamed npm package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants