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 tsoa >= 0.0.45 #11

Closed
danzel opened this issue Aug 14, 2016 · 2 comments
Closed

Cannot install tsoa >= 0.0.45 #11

danzel opened this issue Aug 14, 2016 · 2 comments

Comments

@danzel
Copy link
Contributor

danzel commented Aug 14, 2016

Looks like the location of cli.js changed

C:\Users\dave\Desktop\Code\blah>npm install --save tsoa@0.0.45
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14
npm WARN blah@1.0.0 No repository field.
npm WARN blah@1.0.0 No license field.
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\dave\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "--save" "tsoa@0.0.45"
npm ERR! node v6.3.1
npm ERR! npm  v3.8.5
npm ERR! path C:\Users\dave\Desktop\Code\blah\node_modules\tsoa\dist\cli.js
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod 'C:\Users\dave\Desktop\Code\blah\node_modules\tsoa\dist\cli.js'
npm ERR! enoent ENOENT: no such file or directory, chmod 'C:\Users\dave\Desktop\Code\blah\node_modules\tsoa\dist\cli.js'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

If I grab the tgz from https://registry.npmjs.org/tsoa/-/tsoa-0.0.47.tgz
cli.js is in package\dist\src\cli.js

Probably need to move the file back, or change:
https://github.com/lukeautry/tsoa/blob/master/package.json#L58-L60

Broken by 49730cf AFAICT

@lukeautry
Copy link
Owner

@danzel This should be fixed now, sorry for the inconvenience. Inadvertently changed the output directory structure when I moved over to use new TypeScript 2.0 module resolution features.

@danzel
Copy link
Contributor Author

danzel commented Aug 15, 2016

Awesome thanks, that works now :)

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