JavaScript heap out of memory due to large custom routes about template-odoo

[dduarte-odoogap]

hi @themreza good catch, we are aware of this problem and considering Redis also, but still considering other options.

[odranoelBR]

Hello @themreza , tks for the feedback.
We changed the way of building routes.
Now we don't need generate routes for products anymore, we only use categories as parameters because category slug is part of product route/ slug.
But, the ideia you give, after set all custom routes in redis, you mean nuxt read this routes in build time ?

[themreza]

@odranoelBR As a general note, I'm finding it a bit hard to follow the changes (actually for both the storefront and Odoo modules, e.g. see odoogap/vuestorefront#7 (comment)).

Regarding the route generation, I think we should also assume that the backend has thousands of categories.
Therefore, rather than including the routes into the build, the slug resolution should be done on the server-side.
To speed up the lookup, we can use Redis to cache the routes.