Update bundle/package process as fitting for an npm package #24
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 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.
Fixes #23
See linked issue for background, but with that in mind we will now ship the following (modeled after existing azure sdk packages):
dist/azure-functions.js)dist/azure-functions.min.js)*.js.map) and source code (*.ts) files for debugging purposesThis PR also combines the old build/lint commands to be run from within the webpack command. This reduces the number of commands we have to manually run and avoids problems if you forgot to run one. The downside is that the build may take longer - not terrible on my machine, but we will have to monitor this
I will cherry-pick this to v3.x after it is approved as it should apply to both.