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
I think due to changes here: #6956 that state you can't set both env and jsc.target causes issues with swc/jest. I have an env specified in my .swcrc for bundling code for the web. However, when running jest it complains that env and jsc.target can not be used together. I have tried passing an empty object for env and setting env to null on the custom swc config passed to swc/jest as well as manually reading the .swcrc file and deleting the env property, however I still get an error saying they can not be used together.
I would expect to be able to overwrite the env data by passing a custom swc config object to swc/jest.
Also, the error message itself is fairly cryptic because swc/jest seems to automatically apply a jsc.target implicitly. Its non-obvious as to why this even fails at first.
Actual behavior
Receive an error from jest:
`env` and `jsc.target` cannot be used together
Version
1.3.72
Additional context
No response
The text was updated successfully, but these errors were encountered:
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
Describe the bug
I think due to changes here: #6956 that state you can't set both
env
andjsc.target
causes issues withswc/jest
. I have anenv
specified in my.swcrc
for bundling code for the web. However, when running jest it complains thatenv
andjsc.target
can not be used together. I have tried passing an empty object forenv
and settingenv
tonull
on the custom swc config passed toswc/jest
as well as manually reading the.swcrc
file and deleting theenv
property, however I still get an error saying they can not be used together.Input code
Config
Playground link
No response
Expected behavior
I would expect to be able to overwrite the
env
data by passing a custom swc config object toswc/jest
.Also, the error message itself is fairly cryptic because
swc/jest
seems to automatically apply ajsc.target
implicitly. Its non-obvious as to why this even fails at first.Actual behavior
Receive an error from jest:
Version
Additional context
No response
The text was updated successfully, but these errors were encountered: