fix(amplify-category-function): include files starting with a period on packaging #7861
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.
Description of changes
I use prisma with lambda function and it creates node_modules/.prisma folder to add query-engines. When packaging process, Amplify does not include this folder into build.zip . Adding
dot: true
option to archiver will solve this issue. But it will copy the unwanted files which is starting with period like.env
. So I am not sure this is the best solution. I hope you will find this useful.Description of how you validated changes
Manual
Checklist
yarn test
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.