Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot find module 'typescript' after upgrading to eslint@7.2.0 #2239

Closed
HualiangLI opened this issue Jun 8, 2020 · 1 comment
Closed

cannot find module 'typescript' after upgrading to eslint@7.2.0 #2239

HualiangLI opened this issue Jun 8, 2020 · 1 comment
Labels

Comments

@HualiangLI
Copy link

HualiangLI commented Jun 8, 2020

We got an error as following after upgrading eslint to v7.2.0 which is released 2 days ago:

ERROR in ./src/main.js
Module build failed: Error: Cannot find module 'typescript'
Referenced from: /operation-yh-fi-share/fis-mengine-ui/node_modules/eslint-config-airbnb-base/index.js
Referenced from: /operation-yh-fi-share/fis-mengine-ui/.eslintrc.js
    at Function.Module._resolveFilename (module.js:548:15)
    at Function.Module._load (module.js:475:25)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/operation-yh-fi-share/fis-mengine-ui/node_modules/eslint-plugin-import/lib/ExportMap.js:46:19)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/operation-yh-fi-share/fis-mengine-ui/node_modules/eslint-plugin-import/lib/rules/named.js:7:18)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
 @ multi babel-polyfill ./src/main.js

And after adding and installing typescript, everything works good.

@ljharb
Copy link
Collaborator

ljharb commented Jun 8, 2020

This issue doesn't belong on this repo; and it's already been filed and fixed here, and will shortly be released.

@ljharb ljharb closed this as completed Jun 8, 2020
@ljharb ljharb added the invalid label Jun 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants