Build gives webpack error 98001. Generated engines use disallowed import "node-gyp-build" #34912
Comments
gatsbot
bot
added
the
status: triage needed
|
Hi @john-sc! Sorry to hear you're running into an issue. I wasn't able to reproduce this behavior with I'm on a Mac however, and I don't have a windows machine (virtual or otherwise) to try to reproduce on the same os. I'll check if someone with a windows machine can reproduce this, in the mean time can you verify this also happens with Thanks! |
tyhopp
added
status: awaiting author response
|
@tyhopp gatsby version "^4.0.0", Windows System
|
|
I've faced the same error (Windows 11, Gatsby version: 4.8.0) |
Hi @OlgaBertash , were you able to solve this ? |
LekoArts
added
status: needs reproduction
|
Same error Built Rendering Engines failed validation failed validation. Please open an issue with a reproduction at https://github.com/gatsbyjs/gatsby/issues/new for more help Error: Generated engines use disallowed import "node-gyp-build". Only allowed imports are to Node.js builtin modules o r engines internals. ERROR #98001 WEBPACK Built Rendering Engines failed validation failed validation.
Error: Generated engines use disallowed import "node-gyp-build". Only allowed imports are to Node.js builtin modules or engines internals.
not finished Running gatsby-plugin-sharp.IMAGE_PROCESSING jobs - 11.393s |
|
Please post a minimal reproduction and/or give more information about your environment how we can reproduce this. Thanks! |
with this: |
|
Modules on Installation with yarn 3.2.0 shows node-gyp errors have gotten errors on build with sharp once and imdb every time, this is with Gatsby 4.8.0, 4.7.2 does not give the installation or build errors. These errors do not happen using Gatsby develop. ` ➤ YN0032: │ lmdb@npm:2.2.2: Implicit dependencies on node-gyp are discouraged ➤ YN0032: │ node-addon-api@npm:4.3.0: Implicit dependencies on node-gyp are discouraged ➤ YN0032: │ fsevents@npm:2.3.2: Implicit dependencies on node-gyp are discouraged ➤ YN0032: │ nan@npm:2.15.0: Implicit dependencies on node-gyp are discouraged` I have noticed that You develop Gatsby on Apple computers because fs is used, which will not work on Windows. Test before production on Windows and try to figure out fs-extra. |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Not fixed with clean install on 4.9.1 |
|
Can you try on |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
I also got this issue when running gatsby build but not on gatsby develop. @karnbibek Can you please tell which other package version I have to change, these are the dependencies in my package.json: |
Yes develop was working for me too. and I can see the |
|
This is a gatsby-plugin-sharp error, on Linux it says the below Error: Something went wrong installing the "sharp" module
I have had gatsby-image and now gatsby-plugin-image errors so many times since v 2, I am tired of this non-sense and am going to next which keeps it plugins stable and tests production installations and build on different platforms. Which obviously Gatsby does not, its almost like you are trying to break things. Which puts me and your other users through hell. Most of your packages have outdated modules of which some have been outdated for 5 to 6 years and there are alternatives other npm modules to be used. Go through all plugins you have built and update them or you will keep seeing stupid errors with Gatsby and destroy your customer base. I do not really find any new posts lately on Gatsby anything, all the best programmers in the last year are going to rust or next. Even a lot of the people who build and maintain Gatsby there personal websites are not Gatsby. P.S. If I send a new commit to Github - Nelify with the package-lock.json or yarn.lock, I get the above build error. If I send no lock files it builds, tell y'all anything. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Again, we need a minimal reproduction with clear instructions on what version and system to use. Otherwise we can't help. I've minimized comments that showed some |
|
@LekoArts Try using the git default starter, I did so and and it gave the same error. |
|
It should be fixed, can you make sure all dependencies are up to date? I'm going to close it for now but feel free to re-open. |
|
Chiming in to say it is happening to me as well. There's nothing in the logs that really hint at what's going wrong.
Some of my dependencies and versions: |
|
Gatsby 4.8.1 had issues update to the latest modules. |
|
Following up to say that I fixed it by updating my dependencies, this is my dependency list now: |
|
I'm seeing the same but with
|
|
I am facing this issue.
It's working fine on develop server. Deployed to live linux server. Not getting the above error. No more info is shown.Any suggestion where to look for more info on error |
In development mode everything is working fine. Only production build is failing. |
I've got the same, did you solve that @hesta-inrsaurabh ? |
Preliminary Checks
Description
Cloned from github.
gatsby new fg https://github.com/gatsbyjs/gatsby-starter-default
gatsby develop works fine.
gatsby build gives:
success load gatsby config - 0.023s
success load plugins - 0.641s
...
success Execute page configs - 0.029s
failed Validating Rendering Engines - 0.719s
ERROR #98001 WEBPACK
Built Rendering Engines failed validation failed validation.
Please open an issue with a reproduction at
https://github.com/gatsbyjs/gatsby/issues/new for more help
Error: Generated engines use disallowed import "node-gyp-build". Only allowed
imports are to Node.js builtin modules or engines internals.
child.ts:60 Function._module.default._load
[fg]/[gatsby]/src/utils/validate-engines/child.ts:60:11
loader:1005 Module.require
...
Reproduction Link
https://github.com/gatsbyjs/gatsby-starter-default
Steps to Reproduce
Expected Result
Expected the build to complete without error
Actual Result
Build webpack error 98001
Environment
System: OS: Windows 10 10.0.22000 CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz Binaries: Node: 16.14.0 - C:\Program Files\nodejs\node.EXE npm: 8.3.1 - C:\Program Files\nodejs\npm.CMD Languages: Python: 3.9.6 - /usr/bin/python Browsers: Edge: Spartan (44.22000.120.0), Chromium (98.0.1108.56) npmPackages: gatsby: ^4.8.0 => 4.8.0 gatsby-plugin-gatsby-cloud: ^4.8.0 => 4.8.0 gatsby-plugin-image: ^2.8.0 => 2.8.0 gatsby-plugin-manifest: ^4.8.0 => 4.8.0 gatsby-plugin-offline: ^5.8.0 => 5.8.0 gatsby-plugin-react-helmet: ^5.8.0 => 5.8.0 gatsby-plugin-sharp: ^4.8.0 => 4.8.0 gatsby-source-filesystem: ^4.8.0 => 4.8.0 gatsby-transformer-sharp: ^4.8.0 => 4.8.0 npmGlobalPackages: gatsby-cli: 4.8.0Config Flags
It is unchanged from the repo
The text was updated successfully, but these errors were encountered: