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

nuqs 2 and jest compatibility issue #741

Closed
oyrad opened this issue Nov 5, 2024 · 1 comment · Fixed by #743
Closed

nuqs 2 and jest compatibility issue #741

oyrad opened this issue Nov 5, 2024 · 1 comment · Fixed by #743
Labels
adapters/testing Uses the testing adapter for mocking URL behaviours in tests duplicate This issue or pull request already exists

Comments

@oyrad
Copy link

oyrad commented Nov 5, 2024

Context

What's your version of nuqs?

2.1.1

What framework are you using?

  • ✅ Next.js (app router)

Which version of your framework are you using?

14.2.3

Description

Testing nuqs 2 using jest throws the following error:

Test suite failed to run

This package is ESM only.
See https://github.com/47ng/nuqs/issues/691 for more details.

The linked issue is of no help.

Reproduction

  1. Install nuqs 2.x.x
  2. import { NuqsTestingAdapter } from 'nuqs/adapters/testing' in a test suite
  3. Run any test
  4. Get error

-->

@oyrad oyrad added the bug Something isn't working label Nov 5, 2024
@franky47 franky47 added duplicate This issue or pull request already exists adapters/testing Uses the testing adapter for mocking URL behaviours in tests and removed bug Something isn't working labels Nov 5, 2024
@franky47
Copy link
Member

franky47 commented Nov 5, 2024

See #727 and #737 for solutions. Please try that and report back.

I'll update the error link to point to an aggregate ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
adapters/testing Uses the testing adapter for mocking URL behaviours in tests duplicate This issue or pull request already exists
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants