ssr

What problem does this feature solve?

Example use case:
A static generated app with thousands of routes, like an e-commerce having a route for each product.
Apart from scheduling nuxt generate to run periodically and generate all static and dynamic routes, it would be nice to have the possibility to generate the static files for a single route, for example in a hook when the related ba

Currently, https://quasar.dev/quasar-cli-vite/directory-structure and https://quasar.dev/quasar-cli-webpack/directory-structure look dull.

It can be made interactive, then enrichened with more information and references. Something similar to this might be nice: https://quasar.dev/vu

As stated here - but wrongly closed - prerendering fails when using Axios

Problem is that some libraries like AWS AmplifyJS use Axios under the hood.

@adamdbradley Any idea how to solve this serious issue?

"Babel 7.8.0 supports the new ECMAScript 2020 features by default: you don't need to enable individual plugins for nullish coalescing (??), optional chaining (?.) and dynamic import() anymore with preset-env." - https://babeljs.io/blog/2020/01/11/7.8.0

We should update zero to latest babel and add an integration test for these features. I think the right change will be [here](https://gith

Specific Demand

Like use_future, except instead of taking a Future<Output = T>, takes a futures::Stream<Item = T>

https://emotion.sh/

After this change in Material UI: mui/material-ui#6115

🚀 Feature request

All Razzle examples use Razzle package as dev dependency. Except AfterJS - it needs Razzle as regular dependency because of razzle-dev-utils.

Current Behavior

If Razzle stays as a dev dep, I get this error message in production build:

Error: Cannot find module 'razzle-dev-utils/logger'
 Require stack:
 -  /app/node_modules/@jaredpalmer/after/build/cjs/get