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.

Sign up for GitHub

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

Jump to bottom

Installation failures (using Yarn) #26

Closed
rigsbyt opened this issue May 14, 2020 · 3 comments
Closed

Installation failures (using Yarn) #26

rigsbyt opened this issue May 14, 2020 · 3 comments
Assignees
@aletheia
Labels
bug Something isn't working
Milestone
v2.0.0

Comments

@rigsbyt
Copy link

rigsbyt commented May 14, 2020

Having an issue installing that I think has to do with the usage of NPM (I am using Yarn). This could be a strawman though.

yarn add iam-policy-generator

error <my_package>/node_modules/iam-policy-generator: Command failed.
Exit code: 127
Command: npm run compile && node ./lib/generator/PolicyGenerator.js; tsc ./lib/generated/*.ts
Arguments: 
Directory:<my_package>/node_modules/iam-policy-generator
Output:
> iam-policy-generator@1.1.1 compile <my_package>/node_modules/iam-policy-generator
> tsc

info: Fetching IAM policy metadata from https://awspolicygen.s3.amazonaws.com/js/policies.js 
info: Saving policy file.
info: Generating TS file containing Supported IAM Services enum.
info: Generating TS file containing AWS Service Policies enums.
info: Generating TS file containing ServiceArn
info: library data built. Please import package and have fun!

Actually, it installs everything into node_modules and I can use it, but the error causes it to not persist into my package.json and would cause issues with my CI/CD.
@aletheia
Copy link
Owner

It is a bug we need to fix

@aletheia aletheia added the bug Something isn't working label May 19, 2020
@aletheia aletheia added this to the v2.0.0 milestone May 19, 2020
@aletheia aletheia self-assigned this May 19, 2020
@aletheia
Copy link
Owner

Looks like it's related to Typescript not being available on your machine (it's not your fault, since it is not a requirement). Installing tsc with npm I -g typescript should solve the problem. However, version 2.0 is going to include #19 that removes tsc dependency.

@aletheia
Copy link
Owner

Is going to be solved by #19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aletheia aletheia

Labels
bug Something isn't working
Projects
None yet
Milestone
v2.0.0
Development

No branches or pull requests
2 participants
@aletheia @rigsbyt