swc: unknown field `eval`, expected one of `properties`, ...

Describe the bug

Same kind of issue as #7738 but for a different .terserrc

Input code

.terserrc

{
  "mangle": {
    "eval": true,
    "properties": {
      "regex": "^(?!__core-js_shared__).*_$"
    }
  },
  "compress": {
    "unsafe": true,
    "arguments": true,
    "ecma": "2020",
    "passes": 4,
    "unsafe_arrows": true
  },
  "format": {
    "ecma": 2020
  }
}

Config

No response

Playground link

No response

Expected behavior

No error and similar compression behavior as terser

Actual behavior

parcel.zip

daniel@mmmmmmmmmm parcel % yarn build
🚨 Build failed.

@parcel/optimizer-swc: unknown field `eval`, expected one of `properties`, `props`, `toplevel`, `topLevel`, `keep_classnames`, `keepClassNames`, `keep_fnames`, `keepFnNames`, `keep_private_props`, `keepPrivateProps`, `ie8`, 
`safari10`, `reserved` at line 1 column 324

  Error: unknown field `eval`, expected one of `properties`, `props`, `toplevel`, `topLevel`, `keep_classnames`, `keepClassNames`, `keep_fnames`, `keepFnNames`, `keep_private_props`, `keepPrivateProps`, `ie8`, `safari10`, 
  `reserved` at line 1 column 324

daniel@mmmmmmmmmm parcel % 

Version

@parcel/optimizer-swc@2.9.4

Additional context

No response

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 15 (7 by maintainers)

Commits related to this issue

Most upvoted comments

@danieltroger ~While trying to fix it I found that it works if regex/fancy-regex is enabled. I’ll fix it soon.~

No, the next @swc/core patch version is compatible with what Parcel is requiring. So you’ll just need to bump your lockfile.