Gatsby: Gatsby using deprecated @hapi/joi

[hyecheol123]

Description

Gatsby is depending on the deprecated dependencies

Steps to reproduce

Install Command as guide in official document

• npm install -g gatsby-cli

Expected result

Expecting no warnings for deprecated packages, and expected to see clean output with success message

Actual result

npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.

Environment

System:
OS: Linux 3.10 Debian GNU/Linux 10 (buster) 10 (buster)
CPU: (8) arm64 unknown
Shell: 5.0.3 - /bin/bash
Binaries:
Node: 14.5.0 - ~/.nvm/versions/node/v14.5.0/bin/node
npm: 6.14.5 - ~/.nvm/versions/node/v14.5.0/bin/npm
npmGlobalPackages:
gatsby-cli: 2.12.60

Other Observation

It also complains that the dependency for acorn-dynamic-import is missing (acorn@^6.0.0).
[ERR MSG]

npm WARN [email protected] requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.

[ascorbic]

Thanks for the report. This is because gatsby and gatsby-recipes are using an old version of @hapi/joi for node validation. The newer version is a breaking change, though I don't know if it breaks our schema specifically. If someone wants to take this on, they'd need to look at the changelog for Joi and see if it affects us.

[herecydev]

I'll take a look at this, the changelogs are insanely long so I'll see if it builds first and then go from there

[ascorbic]

Thanks, @herecydev. Much appreciated. If it passes tests, the main issue will be checking for false passes with invalid input.

[herecydev]

Sure I'll see what tests are there and potentially right some further invalid tests

[iAbdullahWaleed]

Hey Guys, This problem prevent me from downloading gatsby, so there is any solution or I should wait?

[mxstbr]

@iAbdullahWaleed deprecated dependencies are warnings when npm installing, not errors, so you should be able to use gatsby anyway? :blush:

[iAbdullahWaleed]

Yes I can, but it's was my first time using the command line, so i was confused when i saw the warnings 🙄.

[mxstbr]

Makes a lot of sense, they are really confusing! Hopefully we can get rid of them soon, until then enjoy Gatsby!

[hyecheol123]

Looks like it is hard to fix this issue, but thanks for all of your hard works and efforts to solve this problem!!
Sorry that I am not able to help the process, as I have no knowledge on Javascript.

[PluckyPrecious]

Hi @mxstbr it's my first time installing Gatsby too, but after getting the deprecated dependencies warning an error occur without complete installation on windows 10.

npm ERR! Unexpected end of JSON input while parsing near '...+oQAJqigTCokVza05RpiQ'
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\HP\AppData\Roaming\npm-cache\_logs\2020-07-30T04_28_22_170Z-debug.log

[aminocode0]

I'm also facing the same issue in my Linux system, please help me to get out from this gatsby error. please help me, anyone

[herecydev]

There's a pr here: https://github.com/gatsbyjs/gatsby/pull/25797

The fix is in progress but it's moving slowly.

[github-actions[bot]]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[pavan-elisetty]

same issue , though @mxstbr said these are warnings but we will be able to use gatsby , but i am unable to use gatsby cli

[adriatic]

This issue is still unresolved (I tripped on it today in a different context, running npm install react-router-dom). Does this mean that that it is the responsibility of the team that maintains the react-router-dom module, or the Gatsby team od Strapi team? Either way why is the process of addressing this issue taking so long?

[herecydev]

@adriatic See this comment: https://github.com/gatsbyjs/gatsby/pull/25797#issuecomment-669392219

If you can help migrate that file; that will unblock this PR.

[adriatic]

I am torn, Dan (@herecydev) by your proposal; encountered this problem doing something very different, so from that point of view the remaining work on this issue is a very low priority for me. On the other hand, probably all people encountering it think the same 😄.

[Code-Tap]

This still appears to be an issue.
Clean first time install