Build succeedes but process hangs forever, making it impossible to deploy with netlify about quasar-app-extension-ssg HOT 6 CLOSED

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 from quasar.conf.js file ?

• Are you tweaking the webpack config via extendWebpack or chainWebpack in quasar.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.

@barnabastoth,

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.