Typescript is invalid

Question

I upgraded angular to 4 and angular cli to 1.03. After I run the command npm ls typescript I get:

+-- @angular/[email protected]
| `-- [email protected]
`-- [email protected]  invalid

npm ERR! invalid: [email protected] C:\development\projects-git\mydoc\static-web\node_modules\typescript

What's the difference between the first and the second typescript, why is the second one invalid/how do I fix it?

I think the error above is the reason why I get the error below so I hope there is a fix for both so I can run my application again.

ERROR in AppModule is not an NgModule
ERROR in ./src/main.ts
Module build failed: TypeError: Cannot read property 'newLine' of undefined
    at Object.getNewLineCharacter (..\static-web\node_modules\typescript\lib\typescript.js:9580:20)
    at Object.createCompilerHost (..\static-web\node_modules\typescript\lib\typescript.js:66674:26)
    at Object.ngcLoader (..\static-web\node_modules\@ngtools\webpack\src\loader.js:202:31)
 @ multi webpack-dev-server/client?http://localhost:4200 ./src/main.ts

basst314 · Accepted Answer · 2017-05-15 12:29:30Z

5

I had a similar issue where i even had two different typescript versions listed when i did npm ls typescript.

What's the difference between the first and the second typescript

The first one is listed as a dependency of @angular/cli, the second one is a dependency of your own project.

why is the second one invalid/how do I fix it?

In my case, i had typescript defined under both, dependencies and devDependencies section in my package.json. I removed it from dependencies and the duplicate output disappeared.

answered May 15, 2017 at 12:29

basst314

1845 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Jan De Dev Over a year ago

Thanks already did that by now but it seems that it wasn't the origin of the error.

basst314 Over a year ago

Instead of upgrading your cli-project, you could try to generate a new one with ng new new-project, copy your src folder (and package.json deps) over and try whether your error persists. If not, take the newly generated configuration files over into your existing project. This solution is easier on smaller projects without lots of customizations, but it may be worth a try even for a more complex scenario.

Collectives™ on Stack Overflow

Typescript is invalid

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related