-
Notifications
You must be signed in to change notification settings - Fork 3k
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
React frontend server won't start with Node 17 #3524
Comments
@dannylee8 Just want to confirm - was this resolved? |
Hi @maggiehays, unfortunately still exists. The issue is: webpack/webpack#14532. However, PR for a doc update was accepted, so I closed the issue. wdyt? |
@dannylee8 hey- looks like the issue you linked on webpack was resolved a few days ago! Can you try again and see if everything is good? |
Hey @dannylee8 - looks like this was addressed & merged! NervJS/taro#10605 Going to keep this issue closed here, but feel free to reopen if needed. |
Hi @gabe-lyons @maggiehays, There's a hack using a switch |
Just an update. Its starting to look like the fix needs to happen in CRA, from the discussion in this issue: facebook/create-react-app#11562 Since Node 16 is LTS, its probably not an issue for datahub users and it looks like the bug is on the way to being rectified, I think this issue can stay closed. Thanks! |
I am trying to setup a local environment and facing an issue with "Datahub-web-react" Issuing the comment "
|
I have the below node version I am too getting the same error as mentioned by @ToanP . Is there a fix for this? |
Describe the bug
Frontend server crashes due to webpack issue in Node 17.
To Reproduce
Steps to reproduce the behavior:
yarn install && yarn start
Expected behavior
React localhost server starts normally.
Desktop (please complete the following information):
Additional context
md5 hash algo is not available on crypto due to OpenSSL update. Reverting to Node 16 (current LTS version) is a workaround.
Issue on webpack is here: webpack/webpack#14532 (closed)
The text was updated successfully, but these errors were encountered: