Skip to content

npm WARN deprecated [email protected] and [email protected] #1137

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

Closed
laticq opened this issue Jul 14, 2019 · 9 comments · Fixed by #1143
Closed

npm WARN deprecated [email protected] and [email protected] #1137

laticq opened this issue Jul 14, 2019 · 9 comments · Fixed by #1143

Comments

@laticq
Copy link

laticq commented Jul 14, 2019

I'm trying to update the parse-dashboard to the latest version, but nothing happens because of the following errors:

npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). 
Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).

npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/boom. 
Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
@davimacedo
Copy link
Member

@laticq thanks for reporting. I also see the warnings but it is running for me besides the messages. Anyway, we need to fix it. @douglasmuraoka could you please take a look on this?

@douglasmuraoka
Copy link
Contributor

I'll take a look into it now. Thanks for reporting @laticq :)

@douglasmuraoka
Copy link
Contributor

douglasmuraoka commented Jul 15, 2019

@davimacedo @acinader looks like #1131 is back due to the package-lock.json change from #1138. To solve this locally, I had to update my npm version to latest and generate a brand new package-lock.json. However, now I'm not secure that It will solve this problem for good since any random build is capable of breaking it again.
Any thoughts?

EDIT: Found another dependency update that would break it #1136

@davimacedo
Copy link
Member

@douglasmuraoka and @acinader please take a look at #1143

@laticq in the meantime, you can install the latest version from the npm instead of the master branch

@Eolykab
Copy link

Eolykab commented Oct 22, 2019

Getting this error. Working fine on my local computer. But not on the server. Was this issue resolved?

@acinader
Copy link
Contributor

yes. are you sure that your server is trying to npm install the latest version of the dashboard (2.0.4)?

@Eolykab
Copy link

Eolykab commented Oct 22, 2019

Yes It is on the latest as well

@acinader
Copy link
Contributor

can you post your npm debug log?

@Eolykab
Copy link

Eolykab commented Oct 22, 2019

I checked on the server. Dokku was not pushing my commits for some reason. It is now working. Thanks

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 a pull request may close this issue.

5 participants