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

1.1.1 Broken - Cannot find module #225

Closed
zaq42 opened this issue Sep 21, 2022 · 4 comments
Closed

1.1.1 Broken - Cannot find module #225

zaq42 opened this issue Sep 21, 2022 · 4 comments

Comments

@zaq42
Copy link

zaq42 commented Sep 21, 2022

Running Cypress gives the following error after upgrading to cypress-tags:1.1.1.

Reverting to 1.1.0 works as expected.

% yarn install   
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 0s 263ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ cypress-tags@npm:1.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0019: │ cypress-tags-npm-1.1.0-e0c1a52a34-c2f5174f17.zip appears to be unused - removing
➤ YN0000: └ Completed
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed
➤ YN0000: Done in 0s 617ms

% yarn test
Couldn't find tsconfig.json. tsconfig-paths will be skipped
Your configFile threw an error from: /.../cypress.config.ts

The error was thrown while executing your e2e.setupNodeEvents() function:

Error: Cannot find module '/.../node_modules/cypress-tags/dist/index.js'. Please verify that the package.json has a valid "main" entry
    at tryPackage (node:internal/modules/cjs/loader:364:19)
    at Function.Module._findPath (node:internal/modules/cjs/loader:577:18)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:942:27)
    at Function.Module._resolveFilename.sharedData.moduleResolveFilenameHook.installedValue [as _resolveFilename] (/.../Library/Caches/Cypress/10.8.0/Cypress.app/Contents/Resources/app/node_modules/@cspotcode/source-map-support/source-map-support.js:811:30)
...
@gavinhenderson
Copy link

Having the same issue 👍

@annaet
Copy link
Contributor

annaet commented Sep 21, 2022

I've been able to replicate this, will look into a fix

@annaet
Copy link
Contributor

annaet commented Sep 21, 2022

Hi @zaq42 / @gavinhenderson

I've just published 1.1.2 which should resolve this issue.

@annaet annaet closed this as completed Sep 21, 2022
@zaq42
Copy link
Author

zaq42 commented Sep 23, 2022

Thanks @annaet

Confirming that 1.1.2 works as expected for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants