You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know that HTML and JavaScript are parsed & edited on every request for those content-types, and that this library is intended for use in development context to facilitate build-free testing/iteration as opposed to in a high volume production web server.
However, I was wondering if there is a suggested way to go about building/converting frontend files (with the same translated paths found in development) when ready for production?
I suppose you could always use a traditional bundle tool like webpack and target a single entry JavaScript file that imports all the modules you'd ever want to use on the client... So, perhaps this might be a silly question 🤔.
I was thinking about somehow utilizing the underlying logic of koa-node-resolve, iterating through all client-side HTML and JavaScript files, translating them using said underlying logic, then copying the resulting files in a build/ directory.
I know that HTML and JavaScript are parsed & edited on every request for those content-types, and that this library is intended for use in development context to facilitate build-free testing/iteration as opposed to in a high volume production web server.
However, I was wondering if there is a suggested way to go about building/converting frontend files (with the same translated paths found in development) when ready for production?
Thanks in advanced!
PS
Awesome library! It works like a charm! 😃 I found it at https://lit.dev/docs/ssr/client-usage/.
The text was updated successfully, but these errors were encountered: