Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content of local plugins referenced by relative path, are not excluded for lambda bundles #7908

Closed
medikoo opened this issue Jul 6, 2020 · 0 comments · Fixed by #10259 · May be fixed by #7931
Closed

Content of local plugins referenced by relative path, are not excluded for lambda bundles #7908

medikoo opened this issue Jul 6, 2020 · 0 comments · Fixed by #10259 · May be fixed by #7931

Comments

@medikoo
Copy link
Contributor

medikoo commented Jul 6, 2020

Use case description

Local plugins listed via relative paths (as ./path/to/plugins - feature introduced with #6261) are not subject to auto exclusion from lambda bundle, as it's the case with plugins put to ./.serverless_plugins folder.

They should be excluded as well.

Proposed solution

  1. When loading plugins build list of all local plugin paths (and store at e.g. pluginManager.localPluginsPaths - it should also include local path)
  2. When generating exclude list, automatically add all those paths to the list
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant