Building with "grunt build" ends up with an error
See original GitHub issueHi,
I have a problem when trying to build react using the installation manual,
running grunt build
ends up immediately with
Running "delete-build-modules" task
Fatal error: spawn node_modules\.bin\gulp ENOENT"
I have Windows 10 x64.
Running gulp
creates all the modules in the build folder so I dont know.
Friend of mine has the same issue.
The reason I am trying to build react is adding custom SVG elements and attributes (more https://github.com/facebook/react/issues/1657#issuecomment-47708471)
Thanks
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
The Command "grunt" exited with code 3 error when building ...
Apparently the error is inside the js file.
Read more >Grunt build/dev error - Adapt Learning Community
I'm trying to run 'grunt dev' in order to develop a theme for my course. I've done the following so far: Create/copy a...
Read more >Getting an error when trying to run grunt build - Google Groups
Hello! I was recently trying to use grunt build task but I get the following error: Fatal error: Perennial task failed: Error: git...
Read more >Configuring tasks - Grunt: The JavaScript Task Runner
When a task is run, Grunt looks for its configuration under a property of the same name. Multi-tasks can have multiple configurations, defined...
Read more >Automated front-end builds with grunt task runner
This is because grunt looks for a file named gruntfile.js that describes the tasks and the configuration of individual tasks. The above error...
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
The problem seems to be in the Grunt config: https://github.com/facebook/react/blob/master/Gruntfile.js#L31. Switching
cmd: path.join('node_modules', '.bin', 'gulp'),
tocmd: path.join('node_modules', '.bin', 'gulp.cmd'),
solves the problem.This bug seems to have been introduced when we switched some build steps to gulp https://github.com/facebook/react/commit/1d0c1b18170768d71105dee55cb8bbd3674f8251.
Thanks for the heads up by the way. You should be able to build now but let us know if you encounter other issues! Nobody on the team is currently building on Windows so I wouldn’t be surprised to see a couple more things like this pop up.