-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
(v2) "ENOENT: no such file or directory" after upgrading from alpha.61 to alpha.62 #3363
Comments
Hi, Have you tried building locally, not on Travis? Is there an option to "clear cache" in Travis or something? |
I only created the Travis build to demonstrate the problem for this issue. It uses a clean workspace each time. The issue happens locally on my mac, and also on Netlify (see this build here https://app.netlify.com/sites/docs-pact-io/deploys/5f4b05887660070007b38902). There may have been some documentation on upgrade steps between 61 and 62 that I missed, but I couldn't find any, and the search wasn't working on the v2.docusaurus website on the weekend. Thanks for looking into it. |
I see the same when building (
Affected PRs (contain links to the builds in checks) |
@TomBrien the dev error is something else. You should get it fixed by using "debug: false" on the classic preset config, but can you help me reproduce it? I tried running your data home assistant repo from master, and upgrading to alpha 62 does not produce this error in dev on my computer. Can you open a dedicated separate issue with repro steps please? I was able to run home assistant both with yarn start and yarn build. Edit:: PR: home-assistant/data.home-assistant#83 Still interested by the dev issue repro |
The same errors occur when running |
@bethesque I am actually running your site, and the error I have in dev is not the same at all. I get a runtime console error: If you look at your package lock on the deps upgrade commit you can see that there's still docusaurus core at alpha 61, that's probably the problem. All deps we provide should be set at the exact same level. Will send a PR once I get your site working on alpha 62 |
PR is there: pact-foundation/docs.pact.io#27 I've opened some new related issues btw: |
@TomBrien can you tell me exactly how you got this error in dev?
With which repo/branch/commit I can reproduce it? Is it gone now or still there? |
Thanks for the quick response and the PR @slorber 🙏 |
Are you on latest version? |
@slorber https://github.com/EarthCubeGeochron/Sparrow/blob/docs-for-master/docs/docusaurus.config.js |
@Idzikowski-Casey I can't even run the branch on alpha 59 locally, is this normal? NPM: Yarn: Also, this is not good, you should have the same version for all docusaurus core packages: It would be much easier for me to find a solution if you had a working base branch, and failing deps upgrade PR. Try using Netlify, it's easy to setup and will simplify our life. |
@slorber I think this issue you are having is due to not having the CLI for our project installed. The To do this, once the Sparrow is cloned run Then try running |
@Idzikowski-Casey unfortunately I don't have time to provide extensive help to everyone. If you want me to help solve this problem, please invest the time to remove your proprietary stuff from your project first and provide me with a regular Docusaurus project that I can simply run by cloning master and yarn install / yarn start. The ideal for me is to have a separate repo with a master deployment working on Netlify, and an upgrade PR that shows the netlify deployment failing. |
Thanks 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:Have you read the Contributing Guidelines on issues?
Yes
To Reproduce
Upgrade from alpha.61 to alpha.62 as per commit pact-foundation/docs.pact.io@e650d27
These two branches show the difference in the package.json and behaviour.
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
Your Environment
Reproducible Demo
As per reproduction steps.
The text was updated successfully, but these errors were encountered: