Do not run webpack on a single non-node function #879
Merged
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
j0k3r
force-pushed
the
fix/skip-single-non-node-function
branch
from
817dc53
to
b87a65c
Compare
j0k3r
force-pushed
the
fix/skip-single-non-node-function
branch
from
b87a65c
to
650e30f
Compare
|
@miguel-a-calles-mba can you check that? 🙏 |
j0k3r
force-pushed
the
fix/skip-single-non-node-function
branch
from
2570230
to
688211a
Compare
|
Is there a way to force webpack to run when running sls deploy function -f myfunctionname? because that's how I was pushing incremental changes "quickly" and testing my graphql server. Or is there a better way to accomplish this. |
|
@oduncan, you should be able to run |
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.
Should fix #755