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

TypeError: Plugin is not a constructor #11

Open
sdrissi opened this issue Oct 25, 2018 · 5 comments
Open

TypeError: Plugin is not a constructor #11

sdrissi opened this issue Oct 25, 2018 · 5 comments

Comments

@sdrissi
Copy link

sdrissi commented Oct 25, 2018

Hey there!

I get a "TypeError: Plugin is not a constructor" when trying to run serverless offline start with serverless-dynamodb-client plugin enabled.

Version I used:

  • serverless v1.32.0
  • node v8.10
  • serverless-offline v3.28.1
  • serverless-dynamodb-local v0.2.35

On top of that I use typescript.

Thanks for the help

@Dimwest
Copy link

Dimwest commented Feb 20, 2020

Experiencing the exact same issue, here is the environment info:

 Operating System:          darwin
 Node Version:              13.6.0
 Framework Version:         1.64.0
 Plugin Version:            3.4.0
 SDK Version:               2.3.0
 Components Core Version:   1.1.2
 Components CLI Version:    1.4.0

Any news on that ?

@Bennyelg
Copy link

Same over here..

@polson
Copy link

polson commented Mar 28, 2020

Also seeing this

@polson
Copy link

polson commented Mar 28, 2020

It means one of your plugins in the serverless.yml plugins section is not actually a serverless plugin

@stewartnoll
Copy link

stewartnoll commented May 7, 2020

Ran the mistake of thinking this was a first-class serverless plugin and when I configured it under plugins in serverless.yml I got the same error (non-typescript project). Not sure if that's what folks in here are experiencing but this is merely a library that abstracts away the localhost config differences btwn running locally vs in AWS that is mentioned here. Removing from the list of plugins in serverless.yml and just using it like any other npm package solved the issue on my end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants