Luis Herranz

We can try two things: - Remove `__webpack_public_path__` declaration from [here](https://github.com/frontity/frontity/blob/dev/packages/core/src/server/public-path.ts) and add it [here](https://github.com/frontity/frontity/blob/dev/packages/core/src/server/middlewares/settings-and-store.ts#L36) (with the correct public path value). - Try modifying the public path value [here](https://github.com/frontity/frontity/blob/dev/packages/core/src/server/middlewares/settings-and-store.ts#L36), but...

What about the things I mentioned in https://github.com/frontity/frontity/issues/913#issuecomment-1082793395? Didn't they work?

I see. I'll try to test `webpack-require-from` and see if I can find a way to solve the TypeScript errors.

@orballo you're going to look into this, right?

I'm not sure how to proceed, to be honest. I've been taking a look myself, but I couldn't find any solution to changing those values at runtime. The variables are...

That sounds promising 🙂

Frontity v2 and switch to [Vite](https://vitejs.dev/)? 😄 I don't know, to be honest. My only idea is to debug the final `server.js` file to try to find the exact moment...

> The memory spikes up, as expected for a stress test, but then settles on the following values: 279mb -> 330mb -> 381mb -> 430mb, and refuses to go down...

Ok. Would you mind trying packages one by one to see which one has the leak (or if it's the core)? Then we can trace back to see the exact...

Oh, I guess you can create a minimal theme then. Something like: ```js const Root = () => ( Empty theme ); const EmptyTheme = { name: "empty-theme", roots: {...