Yuriy Grunin
Yuriy Grunin
You can try [--max-concurrency](https://vuepress.vuejs.org/api/cli.html#max-concurrency) option - it helped me reduce memory usage during a build from ~8G to ~3.5G.
You can try [--max-concurrency](https://vuepress.vuejs.org/api/cli.html#max-concurrency) option - it helped me reduce memory usage during a build from ~8G to ~3.5G.
> You should just use createMemoryHistory from React Router, instead of both the history version and useRouterHistory Ah, right! Haven't noticed that `createMemoryHistory` already contains `useBasename` and `useQueries`. Updated main...
> You might be able to reuse a history across requests but I wouldn't recommend it. Why? What can go wrong if it'll be stateless? It will just be used...
> It seems that createServerHistory.listen is not a function Seems like you're not calling`createServerHistory` but using it as-is. And another question: what is the `history` version you use? This snippet...
Submitted PR that supports this use-case.
Something like this: ``` js app.get('post', '/post/:id', function *() {...}); // Generates url for post with id = 1 var url = app.pathForRoute('post', { id: 1 }); // ==> '/post/1'...
Why not? Almost every serious web framework has such feature. It's very useful and helps you follow DRY principle. I was very surprised that even Express doesn't have this feature...
> i see a lot of edge cases with that What edge cases do you mean?