CODEWITHSUNDEEP
node.jstypescriptcompilationtsconfig
heyJoe
heyJoe

Reputation: 631

node_modules/@types/node/index.d.ts(20,1): error TS1084: Invalid 'reference' directive syntax

I have a problem with typescript compilation. Has anybody else received this error?

node_modules/@types/node/index.d.ts(20,1): error TS1084: Invalid 'reference' directive syntax.

tsconfig.json:

{
    "compileOnSave": false,
    "compilerOptions": {
        "sourceMap": true,
        "outDir": "./dist",
        "rootDir": "./app",
        "target": "es6",
        "module": "commonjs",
        "declaration": false,
        "noImplicitAny": false,
        "removeComments": true,
        "emitDecoratorMetadata": true,
        "experimentalDecorators": true,
        "listFiles": false,
        "skipLibCheck": true
    },
    "include": [
        "./app/**/*.ts"
    ]
}

typescript version in package.json: "typescript": "^2.6.1"

Upvotes: 53

Views: 73387

Answers (10)

Alessandro_Russo
Alessandro_Russo

Reputation: 2191

I add my experience with this error.

For me the problem was generated because I work in a team with different OS.

The issue arises from differences in line endings: Windows uses CRLF (\r\n), while Unix/Linux/Mac use LF (\n). This can cause compatibility problems across systems.

Solution with Git:

On Windows: git config --global core.autocrlf true (converts LF to CRLF on checkout and back on commit).

On Linux/Mac: git config --global core.autocrlf input (keeps LF). This ensures consistent line endings across environments.

After you need to remove node_modules and package-lock.json and run npm i.

Upvotes: 0

Antony Njoroge
Antony Njoroge

Reputation: 11

Try downgrading the @type/node.

I had the same issue with

"devDependencies": {
    "@types/node": "12.20.42",
}

I downgraded it to lower version and it compiles successfully

"devDependencies": {
    "@types/node": "12.19.12",
}

Upvotes: 1

Trilok Singh
Trilok Singh

Reputation: 1353

update TypeScript

npm install typescript@latest --save-dev

Upvotes: 9

Richard Andres Cardozo Lemus
Richard Andres Cardozo Lemus

Reputation: 91

Its worked for me ckeckout your tags for versions of TypeScript. run npm dist-tag ls @types/node and look for your currently typescript version.

Then install the @types/node version supporting for typescript in my case I had to install 14.0.1 version

reference: https://github.com/DefinitelyTyped/DefinitelyTyped/issues/47250#issuecomment-687701880

Upvotes: 9

Sandeep Kumar
Sandeep Kumar

Reputation: 17

I have faced the same problem and found the solution is to update typescript to the latest version from the current version.

Make changes in the package.json file like below:

"devDependencies": {
     "typescript": "^3.9.7"
 }

Now npm install typescript, it will upgrade to the latest version. Then run "ng serve" and it will compile successfully.

Upvotes: -3

sda87
sda87

Reputation: 402

I have faced the same problem and found the solution is to update typescript to the latest version from the current version.

Make changes in the package.json file like below:

"devDependencies": {
     "typescript": "^3.9.7"
 }

Now "npm install typescript" , it will upgrade to latest version. Then run "ng serve" and it will compile successfully.

Upvotes: 22

Walahlah
Walahlah

Reputation: 11

My solution is to change typescript version to '>=2.7.3'. I think the version might depend on other packages. probably need to try a couple of times to get the right version. And don't forget to run install.

Upvotes: 1

Morfing
Morfing

Reputation: 609

Had the same issue. Open the file ../node_modules/@types/node/index.d.ts

and remove the third slash

// <reference lib="es2015" />

compile again

Upvotes: 52

Belle S Rao
Belle S Rao

Reputation: 481

I got the same error. I used the pinned version "@types/node": "7.0.7" in my package.json and got it working.

Upvotes: 38

AlexMasca
AlexMasca

Reputation: 403

Had the same error and the fix was to use the previous version, check the version that you have in package.json for @types/node and see if you have the latest or not. You can check here: https://www.npmjs.com/package/@types/node as it seams that there was a new update.

Upvotes: 3

Related Questions