Question posted in 
I am trying to integrate TypeScript into my React project, created with CRA.
I keep having the following error:
Line 0: Parsing error: DeprecationError: 'originalKeywordKind' has been deprecated since v5.0.0 and can no longer be used. Use 'identifierToKeywordKind(identifier)' instead
I have tried updating
@typescript-eslint/eslint-plugin
@typescript-eslint/parser
to v6 as suggested in several places, but it didn’t solve the issue.
Here’s the partial package.json:
"dependencies": {
"@emotion/react": "^11.10.5",
"@emotion/styled": "^11.10.5",
"@testing-library/jest-dom": "^5.16.4",
"@testing-library/react": "^13.3.0",
"@testing-library/user-event": "^13.5.0",
"@trivago/prettier-plugin-sort-imports": "^4.0.0",
"env-cmd": "^10.1.0",
"eslint": "^8.56.0",
"node-sass": "^8.0.0",
"papaparse": "^5.4.1",
"react": "^18.1.0",
"react-dom": "^18.1.0",
"react-dropzone": "^14.2.3",
"react-router-dom": "^6.3.0",
"react-scripts": "5.0.1",
"sass": "^1.52.1",
"sass-vars-to-js-loader": "^2.1.1",
"web-vitals": "^2.1.4"
},
"devDependencies": {
"@types/react": "^18.2.46",
"@types/react-dom": "^18.2.18",
"@typescript-eslint/eslint-plugin": "^6.18.0",
"@typescript-eslint/parser": "^6.18.0",
"prettier": "^2.8.0",
"typescript": "^5.3.3"
},
"eslintConfig": {
"extends": [
"react-app",
"react-app/jest"
]
},
2
Answers
This is resolved by upgrading to typescript-eslint@6. See Parsing error: DeprecationError: 'originalKeywordKind' has been deprecated since v5.0.0 and can no longer be used.
If you’re still seeing this error, it means that somewhere in your installed packages, an older typescript-eslint version is floating around. Try:
node_modules/directory and re-installingpackage-lock.json,pnpm-lock.yaml,yarn.lock, etc.) and re-installingIf all else fails, you can set
package.jsonoverridesor an equivalent feature for your package manager of choice – to make sure all typescript-eslint packages mentioned in your lockfile are set to v6. But this really should not be necessary. Most of the time, this issue is from out of date packages.After following @Josh’s suggestion above, I found out that the issue for me was stemming from an outdated version of
dependency-cruiser. Per their release notes:After upgrading from v13.0.2 to the latest version, this error went away. Hope that helps!