Sébastien Chopin
Sébastien Chopin
Not much, actually I leverage a `.env` with: ```sh MY_THEME/my/theme/path ``` And use: ``` extends: process.env.MY_THEME || 'my-theme' ``` So can be closed IMO
I like the idea of binding to `process.env` as well so it can stay consistent as in development. But we need to find also a way to make it work...
@DidoMarchet you can use `process.env.MY_ENV` directly inside your server routes and it should works
Line to handle: https://github.com/unjs/nitro/blob/main/src/runtime/renderer.ts#L17
Where is the readme and documentation?
Thank you for the PR! I would also go with the `data-placeholder` attribute seems the `class` is the most easy to understand about what you are styling.
I guess @ineshbose could help
Agree with you, I though about it as well at first and forgot about treeshaking. Will be a breaking chance then, adding it for next major version.
What is your purpose of using it programmatically?
The project is on standby until we have the POC of Nuxt 3 supporting serverless target by default. Otherwise the functions/ would only work for target: "server".