This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
sapper build defaults to build dir, sapper export defaults to export dir
#150
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This closes #133.
sapper buildwill build a production-ready version of the app tobuild, whereupon you can runnode build/server.js(though it probably makes sense to have asapper starttask that's an alias for that).sapper build custom-dirwill build tocustom-dir.sapper exportcurrently exports todist; it will now default toexport(so this will need to be a 0.8 release).sapper export custom-dirdoes exactly what you'd expect.