-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Prerequisites section should have minimal version of runtimes and tools #682
Comments
The current "Installing and Configuring the AWS CDK" section, https://docs.aws.amazon.com/CDK/latest/userguide/install_config.html, has the following under "Prerequisites": You must install Node.js (>= 8.11.x) to use the command-line toolkit and language bindings. If you use Java, you must set the JAVA_HOME environment variable to the path to where you have installed the JDK on your machine to build an AWS CDK app in Java. You must specify both your credentials and a region to use the toolkit, as described in Specifying your Credentials. I'll add the TypeScript info, but who knows the requirements for Java, .NET/C#? |
Assigning to Mathew as he owns the .NET port. |
Here's what I have: CLR version >= 4.5 |
From Aaron for C#: .NET standard 2.0 compatible implementation:
As soon as I publish the updated doc I will provide the URL here and close this issue. |
https://awslabs.github.io/aws-cdk/getting-started.html
With reference to Getting Started, I tried to make TypeScript's AWS CDK app.
In the
Compile the Code
section, I got an error when building TypeScript.https://awslabs.github.io/aws-cdk/getting-started.html#compile-the-code
In
tsconfig.json
, target of compilerOptions is set toES2018
.Therefore, TypeScript needs to be a version supporting ES2018.
ES2018 is supported by TypeScript 2.7.
microsoft/TypeScript#20342
The version of TypeScript installed in my environment is old.
It was solved by installing the latest TypeScript and building it.
It will help peeple like me that using old version TypeScript mindlessly.
The text was updated successfully, but these errors were encountered: