-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
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
Failed to start app with NodeJS newest version v17.0.1 #5778
Comments
BTW as a temporary solution you can use |
At Remotion we managed to fix it using:
|
Hello all, I was able to reproduce the same issue with latest Docusaurus (2.0.0-beta.14). When I updated the Docusaurus along with the Node.js 17 bump on GitHub Actions pipeline (we use Ubuntu latest), the CI job started to fail.
When I added the suggested workaround (capactio/website@b5155b9), the pipeline succeeded (https://github.com/capactio/website/runs/4801264332?check_suite_focus=true). I don't have any issues on macOS Monterey 12.1. Is it something on my end or the bug is still there? Cheers! |
@pkosiec try to re-gen your lockfile and look for older versions of webpack in node modules. If you are using a newer webpack it should work |
Thank you @slorber for your help! While I had correct webpack version in |
* build(docs): update package-lock to v2 The new package-lock version contains more details and is more explicit. Before updating packages with npm it makes sense to update this. * deps(docs): bump docusaurus to 2.0.1 * fix(docs): move hideableSidebar config This fixes the following error at startup: > [ERROR] ValidationError: themeConfig.hideableSidebar has been moved to > themeConfig.docs.sidebar.hideable. * fix(docs): use new algolia appId This was a new requirement from DocSearch. See https://docusaurus.io/blog/2021/11/21/algolia-docsearch-migration for more details. * fix(docs): align new css urls It seems the urls are resolved differently now. The previous urls caused compilation errors during `npm start`. Removing the `feel-scala` prefix fixed these errors. * ci(docs): update to node v18 * deps(docs): update to fix webpack See: - facebook/docusaurus#5778 - TypeStrong/ts-node#1645
* build(docs): update package-lock to v2 The new package-lock version contains more details and is more explicit. Before updating packages with npm it makes sense to update this. * deps(docs): bump docusaurus to 2.0.1 * deps(docs): update to fix webpack See: - facebook/docusaurus#5778 - TypeStrong/ts-node#1645 * deps(docs): install axios for http requests With almost 100k GH stars, this is one of the most commonly used HTTP libraries for nodejs. * deps(docs): install use-editable This library allows us to build an editable React component. * feat(docs): add tutorial-test page Adds a test page (MDX) called `tutorial-test.mdx` to develop the LiveFeel and Editor components. * docs: add tutorial test page to sidebar * make it easy to play around with the new editor Co-authored-by: Philipp Ossler <philipp.ossler@gmail.com>
* chore: update pkg * chore: set static dirs * docs(storage): bouncer ftp update images * build: set build env opt facebook/docusaurus#5778 capactio/website@b5155b9 * docs: update slow ftp
🐛 Bug Report
Starting up the app with the newest NodeJS version (17.0.1) failed with the following error:
Prerequisites
NodeJS version
v17.0.1
Docusaurus newest version
2.0.0-beta.8
npm run clear
oryarn clear
command.rm -rf node_modules yarn.lock package-lock.json
and re-installing packages.Description
After upgrading
Node.js
to the newest version (v17.0.1
), then creating a newDocusaurus
project following the instructions on this page, the project was created successfully but failed when being started withnpm start
. It seems that there is an error related to Nodejs'scrypto
module causing the start of theDocusaurus
app crashed.Have you read the Contributing Guidelines on issues?
YES
Steps to reproduce
Use https://new.docusaurus.io to create a CodeSandbox reproducible demo of the bug.
v17.0.1
Docusaurus
projectnpm init docusaurus@latest mydocs
cd
intomydocs
directory and runnpm start
(currently this command fails to start the app)Expected behavior
Should be able to start up the app
Your environment
The text was updated successfully, but these errors were encountered: