Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC: Change default output directory to match Nitro #1449

Open
2 tasks
brandonroberts opened this issue Nov 19, 2024 · 0 comments
Open
2 tasks

RFC: Change default output directory to match Nitro #1449

brandonroberts opened this issue Nov 19, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@brandonroberts
Copy link
Member

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
@brandonroberts brandonroberts added the enhancement New feature or request label Nov 19, 2024
@brandonroberts brandonroberts self-assigned this Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant