why the types node,jasmine in tsconfig.spec.json?

[stefanaerts]

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

mac osx

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

The log given by the failure.

Normally this include a stack trace and some more information.

when i remove the types jasmin,node from the tsconfig.spec.json file,
npm run test and npm run e2e still work fine for my empty project
I wonder why?

Mention any other details that might be useful.

---

Thanks! We'll be in touch soon.

[Brocco]

When you say "removed from my project" what did that entail?

[stefanaerts]

Sry i was not clear, i removed it from types in tsconfig.spec.json.
And run the test and e2e after that,both worked fine

[filipesilva]

tsconfig.spec.json is used for unit tests only with ng test, and not having them there should give you a couple of errors like what happens when you remove them (and leave an empty array) from tsconfig.e2e.json:

e2e\app.e2e-spec.ts (2,23): Cannot find name 'exports'. (2304)
e2e\app.e2e-spec.ts (3,18): Cannot find name 'require'. (2304)
e2e\app.e2e-spec.ts (4,1): Cannot find name 'describe'. (2304)
e2e\app.e2e-spec.ts (6,5): Cannot find name 'beforeEach'. (2304)
e2e\app.e2e-spec.ts (9,5): Cannot find name 'it'. (2304)
e2e\app.e2e-spec.ts (11,9): Cannot find name 'expect'. (2304)

I tested it right now and it's as you say ng test does not show errors after removing them. This makes me think there's something broken somewhere. Thanks for bringing this up!

[coryrylan]

I think this might be related #5322
To get require to be recognized I added the following in my tsconfig.app.json and now with RC its like it is ignoring the types array.

"types": [
      "node"
    ]

[filipesilva]

Dupe of #5351

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}