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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is the most impactful line, and I think it makes total sense to add it. Thank you!!!
Fwiw, adding to the funcignore will help with one-off deployments from core tools. However, if you deploy through a CI/CD pipeline I would recommend adding
npm prune --production
before deploying, which will more consistently get rid of all dev dependencies.Another fwiw, VS Code will run
npm prune --production
by default if you deploy through there.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
npm prune
is a good shout, I was just trying to do a quick-n-dirty functionapp in this case 😉