Skip to content

Having NGC target es2015 when the project depends on a library that does not provide typings like ramda, installing @types/ramda makes the output code have an incorrect import statement.

Notifications You must be signed in to change notification settings

alvaro450/typings-issue

Repository files navigation

TypingsIssue

This project was generated with Angular CLI version 1.1.0.

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the -prod flag for a production build.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor. Before running the tests make sure you are serving the app via ng serve.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.

About

Having NGC target es2015 when the project depends on a library that does not provide typings like ramda, installing @types/ramda makes the output code have an incorrect import statement.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published