You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to [email protected], our tests started to fail with the following error:
SyntaxError: Unexpected token 'export'
When investigating the issue, we found out it was introduced with this change, as now ../widgets is imported instead of ../widgets/index/index, and where ./answers/answers is imported, where preact is imported.
Preact knows about this issue (preactjs/preact#4406), but for now there is no plan on fixing it.
Thanks, that change wasn't intentional, the import should have only been changed for the types. I'll revert the change in code and you'll be able to verify that works again in your setup.
See #6310 for the PR and instructions on how to try it out in your setup
🐛 Current behavior
After upgrading to
[email protected]
, our tests started to fail with the following error:When investigating the issue, we found out it was introduced with this change, as now
../widgets
is imported instead of../widgets/index/index
, and where ./answers/answers is imported, where preact is imported.Preact knows about this issue (preactjs/preact#4406), but for now there is no plan on fixing it.
For now, I managed to get around this issue by adding a testEnvironmentOptions.customExportConditions jest configuration to our repository:
🔍 Steps to reproduce
npm install
npm run test
Live reproduction
https://github.com/chrisvltn/algolia-jsdom-issue
💭 Expected behavior
Tests to pass without runtime error.
Package version
[email protected]
Operating system
No response
Browser
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: