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

Cannot install library through npm #6

Closed
lucasmotta opened this issue Sep 26, 2020 · 5 comments
Closed

Cannot install library through npm #6

lucasmotta opened this issue Sep 26, 2020 · 5 comments
Labels

Comments

@lucasmotta
Copy link

lucasmotta commented Sep 26, 2020

Hey there, first thanks for creating this package! I've seen your comment on the Prisma repo that you created your own generator to create a json file, which is exactly what I'm after.

The problem is that I cannot install the library through npm:

npm install prisma-json-schema-generator --save-dev
npm ERR! code ENOENT
npm ERR! syscall chmod
npm ERR! path /Users/xxxxx/xxxxx/node_modules/prisma-json-schema-generator/dist/cli.js
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/xxxxx/xxxxx/node_modules/prisma-json-schema-generator/dist/cli.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

My environment:

macOS: 10.15.6
node: 12.18.4
npm: 6.14.6
@valentinpalkovic
Copy link
Owner

@lucasmotta Can you provide some additional information for reproduction reasons?

  • os
  • node version
  • npm Version

@lucasmotta
Copy link
Author

@valentinpalkovic I just updated the main description with my environment - I forgot to add it originally.

github-actions bot pushed a commit that referenced this issue Sep 26, 2020
## [1.1.3](v1.1.2...v1.1.3) (2020-09-26)

### Bug Fixes

* remove bin cli reference from package json ([f0f0a06](f0f0a06)), closes [#6](#6)
@github-actions
Copy link
Contributor

🎉 This issue has been resolved in version 1.1.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@valentinpalkovic
Copy link
Owner

@lucasmotta Please try it with the newest released version (1.1.3). Indeed, there was a wrong configuration in the package.json. Thanks for reporting this bug!

@lucasmotta
Copy link
Author

Nice one @valentinpalkovic, now it works fine! Thank you 👍

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

No branches or pull requests

2 participants