Silent fail on router.js > build in v2.3

Greetings,

I have been using quasar.app.extenions-ssg for almost a year now and it’s great. Recently I ran into some weird errors on BeastCss and upgraded from 2.1.4 to 2.3.0.

Now when I run it with --forceBuild it builds but ends right after finishing the build and before starting generate.

I started debugging (by putting console.log in the source code of ./node_modules/quasar-app-extension-ssg) and I found that it’s failing silently (no error whatsoever) when it cannot get routerBuildPromise resolved ever. I found that it’s related to the new router.js that is supposed to kick and spit the routes I guess. (This commit: https://github.com/freddy38510/quasar-app-extension-ssg/commit/5b33845747f5578eabac74a051701489b8856b9a#diff-09b963845cb446391f74c8ba93ecd69d85db6f97f6d03fa997297be1264a7349)

Here is a screenshot of the logs and my code. (I am sorry that the project is so big and private that I cannot share a repo/demo.)

If I simply skip ensureBuild function (put a return; at the top of it) and instead run a build manually, everything works.

I am going to dive deeper but meanwhile wanted to ask if you have any idea/clue/suggestion? I will update this issue with any findings/solution that I get to.

Thanks again for this awesome work @freddy38510!

[freddy38510]

You sum it up perfectly here. I really appreciate that you take the time to do that.

Actually the issue (on the 2.x branch) about running two instances of webpack concurrently will be solved in the next commits.

(If you are curious, please see this commit, and more particularly this file https://github.com/freddy38510/quasar-app-extension-ssg/blob/master/src/build/webpack/ssg/generator.js#L64 and this one https://github.com/freddy38510/quasar-app-extension-ssg/blob/master/src/build/templates/entry/ssg-get-app-routes-entry.js)

You brought up the right point by asking the question “do we need it?”. I want to give as much flexibility as possible to the end user, so I will provide an option to disable this feature.

The process should still take a reasonable amount of time to run. In your case, with a lot of vue components to compile, I hope that externalizing vue components instead of replacing it will significantly reduce this amount of time.

[eyedean]

Thank you @freddy38510. I will update the package in the next release and will let you know about the result!