(v2) "ENOENT: no such file or directory" after upgrading from alpha.61 to alpha.62
See original GitHub issueThanks for everyone’s work on this awesome product. It has been really useful for us.
🐛 Bug Report
When running npm run build
after upgrading from alpha.61 to alpha.62, the website does not build, and this output is repeated for many/all pages:
(node:35940) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/Users/me/workspace/pact-foundation/docs.pact.io/website/.docusaurus/docusaurus-plugin-content-docs/default/site-docs-pact-broker-2-lib-pact-broker-doc-views-index-pacticipant-version-tag-md-c69.json'
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce
Upgrade from alpha.61 to alpha.62 as per commit https://github.com/pact-foundation/docs.pact.io/commit/e650d27f768c69805bd8822122f0274ff063a555
These two branches show the difference in the package.json and behaviour.
git clone git@github.com:pact-foundation/docs.pact.io.git
cd docs.pact.io/website
npm i
npm run build # this will succeed, as it's on alpha.61
git checkout chore/docusaurus-alpha-62
npm i
npm run build # this hangs and has numerous lines of error output
Expected behavior
Build completes successfully as per https://travis-ci.com/github/pact-foundation/docs.pact.io/builds/181930983
Actual Behavior
Build hangs, screen is filled with errors in the following format, as per https://travis-ci.com/github/pact-foundation/docs.pact.io/builds/181931029
(node:35940) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/Users/me/workspace/pact-foundation/docs.pact.io/website/.docusaurus/docusaurus-plugin-content-docs/default/site-docs-pact-broker-2-lib-pact-broker-doc-views-index-pacticipant-version-tag-md-c69.json'
Your Environment
- Docusaurus version used: docusaurus/core 2.0.0-alpha.62
- Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0): node v12.0.0
- Operating system and version (desktop or mobile): Mac desktop
Reproducible Demo
As per reproduction steps.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:15 (1 by maintainers)
Top Results From Across the Web
npm WARN enoent ENOENT: no such file or directory, open 'C ...
chat folder. But when I run following command it shows following Warnings.And its not created a node_modules directory inside my project folder.
Read more >"/dev/fd/63 No such file or directory" - Ask Ubuntu
I've been trying to run a command in chroot (pretty new to this), and I get the following output. root@hostname:~ # bash <(wget...
Read more >HsB - River Thames Conditions - Environment Agency - GOV.UK
Anthony west author, Igoogle homepage not working, Kukatakan dgn indah chord, ... Bert par, Jana luttropp youtube, Enoent no such file or directory, ......
Read more >812624 – Gnome Shell constantly using > 100% cpu load
if you mkdir -p the directories that it says "No such file or directory" for ... When upgraded to systemd{,-sysv}-44-17, the Gnome Shell...
Read more >https://web.mit.edu/freebsd/head/contrib/tcsh/Fixes
Avoid infrequent exit when tcsh cd's into a non-existent directory ... Don't rebuild needlessly when generated files are unchanged (Martin Kraemer) 62.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for the quick response and the PR @slorber 🙏
I see the same when building (
yarn build
) on Netlify. When running the development server (yarn start
) I am seeing:Affected PRs (contain links to the builds in checks) home-assistant/data.home-assistant#81 home-assistant/data.home-assistant#82 home-assistant/developers.home-assistant#628 home-assistant/developers.home-assistant#629 home-assistant/companion.home-assistant#318 home-assistant/companion.home-assistant#319