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 is a way to disable the plugin.
Unhandled rejection Error: ENOENT: no such file or directory, symlink 'home/../node_modules' -> '/home/.build/node_modules'
We use plugin for serverless project. There are few different stacks and we use parametrized serverless to include what we need for every specific stack. Sometimes we only wrap cloudformation template within serverless and deploy it. That was a requirement.
When we don't have functions (lambdas) within that stack and have only wrapped cloudformation template, plugin throws the following error:
Unhandled rejection Error: ENOENT: no such file or directory, symlink 'home/../node_modules' -> '/home/.build/node_modules'
That means that serverless don't create .build aidirectory because plugin can not exclude node_modules and than deploying and packaging fails.
Obviously, we need possibility to disable plugin at least in this situation. I added 2 ways to do that.
1.Adding a typescriptPlugin section to the custom section of your serverless.yml to set default value if needed:
--typescript-plugin [disabled|off|false]
The second option will override default value.