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
Which scope/s are relevant/related to the feature request?
vite-plugin-nitro
Information
Currently, we use a custom output directory. dist/analog/public for static assets and dist/analog/server for the built server. Depending on the deployment provider, the output directory could also change. We have some workarounds for special cases today.
This change would use Nitro's default .output directory at the root and use a different directory for interemediate builds assets like client, ssr, and .nitro.
This would be introduced using a flag, and the default would be flipped in Analog 2.0.
Describe any alternatives/workarounds you're currently using
No response
I would be willing to submit a PR to fix this issue
Yes
No
The text was updated successfully, but these errors were encountered:
Which scope/s are relevant/related to the feature request?
vite-plugin-nitro
Information
Currently, we use a custom output directory.
dist/analog/public
for static assets anddist/analog/server
for the built server. Depending on the deployment provider, the output directory could also change. We have some workarounds for special cases today.This change would use Nitro's default
.output
directory at the root and use a different directory for interemediate builds assets likeclient
,ssr
, and.nitro
.This would be introduced using a flag, and the default would be flipped in Analog 2.0.
Describe any alternatives/workarounds you're currently using
No response
I would be willing to submit a PR to fix this issue
The text was updated successfully, but these errors were encountered: