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

The latest version installed by npm is different than what is in the repo #302

Open
bishoybt opened this issue Sep 11, 2023 · 1 comment

Comments

@bishoybt
Copy link

Actual Behaviour

When I run npm install as directed in the README, I get the version 0.2.40 installed. This version doesn't handle the docker flag mentioned in the README as well, and in the documentation at https://www.serverless.com/plugins/serverless-dynamodb-local.

Expected Behaviour

I expect the installation by npm to be same like a tag or a branch in this repo so that I can find out which version is having which feature. At the moment I cannot use the docker feature because it is not supported in version 0.2.40 that is available by npm install. Furthermore, I cannot find a tag or a branch with the value 0.2.40. The version 0.2.40 though is still the current version in the package.json file in the repo.

Steps to reproduce it

  1. Run npm install serverless-dynamodb-local. Notice the installed version will be 0.2.40.
  2. Run serverless dynamodb start --docker
  3. An error stating that the flag docker is not recognizable.
  4. Find the installed packages for serverless-dynamodb-local and examine the README file.
  5. The README file doesn't include the docker flag which indicates a different version than what is currently in the repo and the online documentation.

Would you like to work on the issue?

Yes. With some guidance.

@domjancik
Copy link

domjancik commented Jan 17, 2024

Running into the same issue. For better searchability, the error is Detected unrecognized CLI options: "--docker".

It seems that this repo is dead, however there is a maintained fork that both fixes this docker issue and vulnerable dependencies, see post in another issue: #262 (comment)

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

2 participants