CI WSL Error: Cannot find module 'semver' #2737
Comments
AndyOGo
changed the title
|
I'm aware of this, but I'm not sure what's causing it. I'd love a PR that can fix it (or alternatively, migrate windows tests to GHA). |
|
I found an issue over there from 2019, which is closed That fix landed in Latest is But mocha is far behind here. npm ls mocha
eslint-plugin-import@2.27.5 /eslint-plugin-import
├─┬ eslint-import-resolver-node@0.3.7 -> ./resolvers/node
│ └── mocha@3.5.3 deduped
├─┬ eslint-import-resolver-webpack@0.13.2 -> ./resolvers/webpack
│ └── mocha@3.5.3 deduped
└── mocha@3.5.3Anyway npm list semver
eslint-plugin-import@2.27.5 /eslint-plugin-import
├─┬ @typescript-eslint/parser@5.55.0
│ └─┬ @typescript-eslint/typescript-estree@5.55.0
│ └── semver@7.3.8
├─┬ babel-plugin-istanbul@4.1.6
│ ├─┬ istanbul-lib-instrument@1.10.2
│ │ └── semver@5.7.1
│ └─┬ test-exclude@4.2.3
│ └─┬ read-pkg-up@1.0.1
│ └─┬ read-pkg@1.1.0
│ └─┬ normalize-package-data@2.5.0
│ └── semver@5.7.1
├─┬ babel-preset-airbnb@2.6.0
│ └─┬ babel-preset-env@1.7.0
│ └── semver@5.7.1
├─┬ eslint-doc-generator@1.4.3
│ └─┬ @typescript-eslint/utils@5.55.0
│ └── semver@7.3.8
├─┬ eslint-import-resolver-webpack@0.13.2 -> ./resolvers/webpack
│ └── semver@5.7.1
├─┬ eslint-plugin-import@2.27.5
│ └── semver@6.3.0 deduped
├─┬ nyc@11.9.0
│ ├─┬ istanbul-lib-instrument@1.10.1
│ │ └── semver@5.5.0
│ └─┬ test-exclude@4.2.1
│ └─┬ read-pkg-up@1.0.1
│ └─┬ read-pkg@1.1.0
│ └─┬ normalize-package-data@2.4.0
│ └── semver@5.5.0 deduped
├─┬ safe-publish-latest@2.0.0
│ └── semver@7.3.8
├── semver@6.3.0
└─┬ typescript-eslint-parser@22.0.0
└─┬ typescript-estree@18.0.0
└── semver@5.5.0 |
|
I cloned npm list -prod semver
mocha@3.5.3 /mocha
└── (empty)npm list -dev semver
mocha@3.5.3 /mocha
├─┬ karma@1.3.0
│ └─┬ log4js@0.6.38
│ └── semver@4.3.6
├─┬ nyc@11.9.0
│ ├─┬ istanbul-lib-instrument@1.10.1
│ │ └── semver@5.5.0
│ └─┬ test-exclude@4.2.1
│ └─┬ read-pkg-up@1.0.1
│ └─┬ read-pkg@1.1.0
│ └─┬ normalize-package-data@2.4.0
│ └── semver@5.5.0 deduped
├─┬ os-name@2.0.1
│ └─┬ win-release@1.1.1
│ └── semver@5.7.1
└─┬ phantomjs@1.9.8
└─┬ npmconf@0.0.24
└── semver@1.1.4 |
|
Yes, we're stuck on mocha v3. Does that depend on node-environment-flags? Maybe a workaround is to manually install a fixed version of it. |
|
I missed the obvious.
|
|
Good call, and it's in the project's |
|
Indeed. I googled that error. These sources suggest that
|
|
All of that is handled in appveyor.yml - PRs are quite welcome :-) |
|
I created just a workaround and excluded the remaining WSL jobs. A proper solution is still required. |
|
I prefer to leave them failing rather than skip them. |
|
I understand. |
|
@ljharb |
All jobs with WSL config fail on
master.https://ci.appveyor.com/project/ljharb/eslint-plugin-import/builds/46338908
E.g.:
https://ci.appveyor.com/project/ljharb/eslint-plugin-import/builds/46338908/job/hqyre5h5sbfqqn44
The text was updated successfully, but these errors were encountered: