-
Notifications
You must be signed in to change notification settings - Fork 4.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
Errors during the build process #37123
Comments
I am also a Windows user and have encountered the exact same symptoms. The build succeeded by following the fast-glob documentation and replacing the path separator in the two files as shown below.
const PACKAGES_DIR = path.resolve( __dirname, '../../packages' );
// to
const PACKAGES_DIR = path.resolve( __dirname, '../../packages' ).replace( /\\/g, '/' ); I think it is not enough to just modify these two since the Hopefully this information will help you fix it. |
I looked into it, and this is a fix that is only needed for some tasks that use fast-glob. |
In the changelog for fastglob 3:
So that might explain it. |
This has been solved, so I am closing this issue. |
Description
I am unable to build the plugin from trunk.
npm install
-no errors reportedOn
npm run build
:Error 1:
I wonder if this is related to the upgrade of fast-glob:
https://github.com/WordPress/gutenberg/pull/36260/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519L172
If I revert fast-glob back to version 2.2.7, I do not have any build errors, but I am unsure of what other issues that may cause.
(I don't even know what a glob is...) I do not know how to troubleshoot it further, or if I need to open an issue here? https://github.com/mrmlnc/fast-glob/
Error 2:
There are several packages that can't be resolved, I only copied the first message.
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
Environment info
Windows 10.
NPM 6.14.15.
Node v14.17.3.
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: