Comments (6)
Hi @barnabastoth I really appreciate that you find this extension useful.
I tried to replicate the issue on linux with a clean install and latest versions of quasar packages, but without success.
-
Are you using any hooks
beforeBuild, afterBuild, onRouteRendered, afterGenerate
fromquasar.conf.js
file ? -
Are you tweaking the webpack config via
extendWebpack
orchainWebpack
inquasar.conf.js
file ? -
Are any other extensions running? From the logs you provided it appears not but I'm asking anyway.
-
Did you try to build your app in ssg mode with
quasar build -m ssg
?
This could be from old cached files from previous builds with older versions of the extension.
You can try running the quasar clean
command to be sure.
from quasar-app-extension-ssg.
Hey Freddy
Thanks for the quick response.
- I am using the beforeBuild hook to gather the dynamic ids, which seems to run fine, and all the pages get generated.
- I am not tweaking the extendWebpack or chainWebpack
- No, i am not using any other quasar extension
- I am using the command: quasar ssg generate -d
If I add process.exit(0) to the afterGenerate hook, everything is working and I am able to deploy to netlify, tho I guess this is not the perfect solution.
I will try quasar clean once I get home.
The issue has to be on my side, but im not quite sure what. I just added your extension to another quasar project of mine and the process exits properly, eventho the two project has the same quasar + extension version.
Is there a way to debug this more?
Thanks again for your work, you are a lifesaver:)
from quasar-app-extension-ssg.
From what you said I'm suspecting the beforeBuild hook. Are you opening some connections to a database ?
I just found two Node.js functions that should be helpful for debugging: process._getActiveHandles()
and process._getActiveRequests()
.
You could run these functions in the afterGenerate
hook. There are also some packages that use these functions and can give you more clues like why-is-node-running.
from quasar-app-extension-ssg.
I am connecting to a Meteor server with the simple-ddp package to get the IDS to generate the routes, it is a socket connection, but I do receive the data and everything correctly. Dont quote me on this, I will verify but I believe I also tried to remove the beforeBuild hook and the issue was the same.
Tomorrow I will try those functions and get back to you, thank you
from quasar-app-extension-ssg.
Might be a WebSocket connection still open.
Are you calling the disconnect method at the end of the beforeBuild
hook ?
Do you connect to your Meteor server at server-side when the pages are pre-rendered ?
from quasar-app-extension-ssg.
By the way, if the goal of your beforeBuild
hook usage is to get a list of IDS to generate an array of dynamic routes, you don't have to since the crawler
feature will take care of dynamic routes.
Any news about your issue ?
from quasar-app-extension-ssg.
Related Issues (20)
- error when using meta HOT 1
- ssg gets fallback to SPA when router has query
- Render markdown to SSG HOT 1
- Missing Vite.js v3/v4 support HOT 7
- searchForWorkspaceRoot is not a function HOT 10
- Demo is no longer can be used as a template HOT 4
- Error [ERR_REQUIRE_ESM]: require() of ES Module inside quasar-app-extension-ssg's server-entry.js HOT 2
- pinia persisted state: storages (session storage) HOT 2
- I get the error message "Cannot find module 'ouch''" when running "quasar ssg dev" on freshly scaffolded quasar project HOT 3
- vue-loader & css-loader throwing errors HOT 12
- minifyOptions error? HOT 1
- Failed to add extension due to workbox-build version HOT 2
- Cannot find module `.cache/quasar-app-extension-ssg/server/server-entry.js` HOT 2
- `TypeError: Cannot read properties of undefined (reading 'get')` in `server-entry.js` during generation HOT 7
- Using Pinia from library results in `TypeError: can't access property "_s", pinia is undefined` HOT 3
- Empty data on all pages except one, when routes uses same component HOT 1
- feat: update to Vite 5 and @quasar/app-vite dependency to ^2.0.0
- ERR_INVALID_ARG_TYPE HOT 7
- use build-time fs paths for inline content embedding
- Error [ERR_REQUIRE_ESM]: require() of ES Module ..../node_modules/quasar/lang/en-GB.js from ..../node_modules/.cache/quasar-app-extension-ssg not supported. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from quasar-app-extension-ssg.