-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[Bug] docz fails to run when upgrading to yarn@berry #1024
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
Comments
I was able to get some debug hints from running Adding these to dependencies:
And these to devDependencies:
Appear to have moved me closer to what I want, but the config is now unable to resolve the npm WARN lifecycle The node binary used for scripts is /tmp/tmp-17846NC3MwdeViYgb/node but npm is using /usr/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
> docz-app@ build /home/dannyrb/code/Viewers/platform/ui/.docz
> gatsby build "--prefixPaths" "/"
ERROR #10226 CONFIG
Couldn't find the "gatsby-theme-docz" plugin declared in "/home/dannyrb/code/Viewers/platform/ui/.docz/gatsby-config.js".
Tried looking for a local plugin in /home/dannyrb/code/Viewers/platform/ui/.docz/plugins/gatsby-theme-docz.
Tried looking for an installed package in the following paths:
- /home/dannyrb/code/Viewers/.yarn/unplugged/gatsby-virtual-c3f5930f7a/node_modules/gatsby/dist/bootstrap/load-themes/node_modules/gatsby-theme-docz
- /home/dannyrb/code/Viewers/.yarn/unplugged/gatsby-virtual-c3f5930f7a/node_modules/gatsby/dist/bootstrap/node_modules/gatsby-theme-docz
- /home/dannyrb/code/Viewers/.yarn/unplugged/gatsby-virtual-c3f5930f7a/node_modules/gatsby/dist/node_modules/gatsby-theme-docz
- /home/dannyrb/code/Viewers/.yarn/unplugged/gatsby-virtual-c3f5930f7a/node_modules/gatsby/node_modules/gatsby-theme-docz
- /home/dannyrb/code/Viewers/.yarn/unplugged/gatsby-virtual-c3f5930f7a/node_modules/gatsby-theme-docz
- /home/dannyrb/code/Viewers/.yarn/unplugged/node_modules/gatsby-theme-docz
- /home/dannyrb/code/Viewers/.yarn/node_modules/gatsby-theme-docz
- /home/dannyrb/code/Viewers/node_modules/gatsby-theme-docz
- /home/dannyrb/code/node_modules/gatsby-theme-docz
- /home/dannyrb/node_modules/gatsby-theme-docz
- /home/node_modules/gatsby-theme-docz
- /node_modules/gatsby-theme-docz |
Hi! 👋 This issue looks stale, and doesn't feature the Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolution faster). It helps us help you! 😃 If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the |
Describe the bug
I have a monorepo. A project in our monorepo uses
docz
for its component library.[email protected]
usesgatsby
under the hood. When runningyarn run dev
, which executes the boilerplate npm scriptdocz dev
, I receive an error that I do not receive when using yarn1.22.x
To get the command to run at all, I've had to modify my
.yarnrc.yml
:To Reproduce
The minimal information needed to reproduce your issue (ideally a package.json with a single dep). Note that bugs without minimal reproductions might be closed.
I will circle back to add a reproduction; I wanted to get this issue up before I packed up for the day.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment if relevant (please complete the following information):
Additional context
docz does this odd thing where the project contains a
.docz
directory that contains an autogenerated gatsby project (with webpack config and package.json). This project is where the webpack process is started. I'm unsure of if this extra nesting causes issues.I have included the
gatsby-node.js
PnpWebpackPlugin snippet.The text was updated successfully, but these errors were encountered: