alpha: expose underlying nitro configuration in vite plugin #4192
+32,016
−21,926
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RELEASE_ALL
RELEASE_ALL
Currently, none of the packages (i.e `packages/*`) need `vite`
bundled as a `dependency`. So its been moved to the
`devDependencies` and had the version opened using
`"peerDependencies": { "vite": ">=6.0.0" }`.
Additionally, `vite` has been added as a `dependency` to
the Start end-to-end sandboxes.
In a later PR, `vite` will need to be added to all the
TanStack Start examples (i.e. `examples/**/start-*`).
…anStack#4137) Only import `routeCode` if `node.fullPath` is available.
…t + matching server function handler route on Windows (TanStack#4146)
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
|
this will be soon possible via the nitro vite plugin |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was having some build issues across multiple platforms - I figured I'd have a better chance of resolving them if the nitro config was exposed.
Any edge cases I might be missing here? Wondering why this was omitted in the first place.