[WIP] use external generator for SSR #1718
Closed
Conversation
This file contains 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
|
Starting to have second thoughts about this — as I work through it, I'm starting to realise just how much juggling would be involved. We'd need separate packages for generators, utilities, types, shared helpers... I think we're better off just organising the codebase a bit better. This process has given me a couple of ideas. |
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.
Making a start on #1678. Beginning with SSR, since that's the easiest to break out.
The contract between the two modules isn't quite settled yet. Also, some utilities will need to be moved into a separate package (let's call it
@sveltejs/utils) to avoid duplication.The
@sveltejs/generate-ssrrepo is here: https://github.com/sveltejs/generate-ssr