`gridsome build` hangs after Compile assets
See original GitHub issueDescription
Upon creating a new, OOTB project and running gridsome build
, it hangs after Compile assets and never creates any HTML files.
Steps to reproduce
- Install the gridsome cli:
sudo npm install --global @gridsome/cli
- Create the project:
gridsome create ttoo
cd ttoo
- Build with
gridsome build
Expected result
A /dist
folder with HTML, JS and CSS etc.
Actual result
gridsome build
Gridsome v0.5.7
Initialize - 0.45s
Load sources - 0.03s
Create GraphQL schema - 0.03s
Set up routes - 0s
Generate code - 0.02s
Bootstrap finish - 0.54s
Run GraphQL (0 queries) - 0s
Compile assets - 3.15s
A /dist
folder with:
/assets/css/*styles..css
/assets/js/app|component|page*.js
/assets/manifest/client|server.json
Environment
Libs:
- gridsome version: 0.5.7
- @gridsome/cli version: 0.0.9
For Tooling issues:
- Node version: 10.15.3
- Platform: Mac 10.14.4
Others:
- Yarn version: 1.15.2
Issue Analytics
- State:
- Created 4 years ago
- Reactions:9
- Comments:26 (8 by maintainers)
Top Results From Across the Web
Gridsome Build fails (Yep, checked the other posts)
I'm trying to deploy a basic gridsome site from github. I've configured Netlify with the build command: gridsome build , and the publish...
Read more >Grisome build succeeds locally but fails on AWS Amplify
This appears to be a bug where Gridsome runs out of memory processing a large number of large files. This workaround preprocesses all...
Read more >Troubleshooting
If you have problems after upgrading try remove .cache and node_modules folder and run yarn again. Edit this page on GitHub.
Read more >Gridsome is not that Ready for PWA - AC Dustbin
How I am tring to build a nice gridsome-generated site with PWA support 虽然可以勉强并入“用 Vue ... So I turns on assets hashing manually:...
Read more >module.updatehash: use new chunkgraph api - ...
Next.js working fin in dev mode but not on build ... Next js build hangs forever ... DeprecationWarning: Compilation.assets will be frozen in...
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
I also experienced this and tried to do some debugging. It works when downgrading
vue-router
. Can anyone else confirm this? Try adding this topackage.json
and reinstall dependencies with Yarn:@vandelay87 Your SVGs should be fine. This bug is caused by a change in the latest version of
vue-router
. I’ll publish a fix later today 😃