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
exportdefault{collectCoverage: true,collectCoverageFrom: ['**/src/**/*.js'],coverageProvider: 'babel',coverageReporters: ['text','text-summary'],modulePathIgnorePatterns: ['dist'],/** * Use alternative runner to circumvent segmentation fault when * webpack's node.js API uses dynamic imports while running * jest's v8 vm context code. * * @see https://github.com/nodejs/node/issues/35889 * @see https://github.com/nodejs/node/issues/25424 */runner: 'jest-light-runner',testMatch: ['**/__tests__/**/*.spec.js'],transform: {}}
I've noticed that you provide ESM and CJS builds via conditional exports in your package.json file. I believe this error is because you do not include "type": "module" in your package.json file so that consumers attempting to load the ES variant of astravel from an ES module context trigger the exception.
The text was updated successfully, but these errors were encountered:
While running Jest against tests for an ES module that uses
astravel
as a dependency, I encountered the following SyntaxError:package.json
jest.config.spec.js
I've noticed that you provide ESM and CJS builds via conditional
exports
in your package.json file. I believe this error is because you do not include"type": "module"
in your package.json file so that consumers attempting to load the ES variant ofastravel
from an ES module context trigger the exception.The text was updated successfully, but these errors were encountered: