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
{{ message }}
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.
This seems fine for projects that are targetting the browser (eg @neutrinojs/web, ...), however for @neutrinojs/node or @neutrinojs/library (with target: 'node') a more suitable value for testEnvironment would be 'node'.
I'm not sure of the best way of checking within @neutrinojs/jest when to override the environment - hardcoding presets is a non-starter, so perhaps by inspecting the babel preset-env compile targets?
The text was updated successfully, but these errors were encountered:
Currently the
@neutrinojs/jest
preset doesn't definetestEnvironment
, so Jest uses the default of'jsdom'
:https://jestjs.io/docs/en/configuration.html#testenvironment-string
This seems fine for projects that are targetting the browser (eg
@neutrinojs/web
, ...), however for@neutrinojs/node
or@neutrinojs/library
(withtarget: 'node'
) a more suitable value fortestEnvironment
would be'node'
.I'm not sure of the best way of checking within
@neutrinojs/jest
when to override the environment - hardcoding presets is a non-starter, so perhaps by inspecting the babel preset-env compile targets?The text was updated successfully, but these errors were encountered: