Update dependency @swc/core to v1.3.84

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@swc/core (source)	1.3.80 -> 1.3.84

---

Release Notes

swc-project/swc (@​swc/core)

v1.3.84

Compare Source

Bug Fixes

• (es/codegen) Emit leading comments for ExprStmt (#​7916) (2da5895)

• (es/codegen) Use emitAssertForImportAttributes (#​7936) (dac8888)

• (es/compat) Visit assign expr in generator (#​7932) (97068e1)

v1.3.83

Compare Source

Bug Fixes

• (css/modules) Aggregate class names when composes is chained. (#​7917) (0db25a2)

• (es/module) Revert #​7901 (#​7906) (85d6e9b)

• (es/module) Fix jsc.paths for projects using pnpm (#​7918) (a86e9f3)

Features

• (es/codegen) Add an option to print assert for import attributes (#​7914) (ee75756)

v1.3.82

Compare Source

Bug Fixes

• (common) Fix logic for excluding FileName from source maps (#​7900) (aa64955)

• (es/module) Make jsc.paths fully resolve TypeScript files (#​7901) (c714dd2)

• (es/resolver) Correctly resolve global value (#​7893) (2db10e9)

v1.3.81

Compare Source

Bug Fixes

• (es/codegen) Fix placing of comments of yield arguments (#​7858) (122d14c)

• (es/compat) Apply transforms for explicit resource management (#​7881) (3180e68)

• (es/compat) Make SwitchCase handler of block-scoping stateless (#​7888) (4b33d41)

• (es/dep-graph) Analyze import type children (#​7883) (057bd5f)

• (es/minifier) Report is_fn_local even if var is hoisted (#​7876) (87a47bf)

• (es/module) Don't create absolute paths for jsc.paths on Windows (#​7892) (5fbc251)

• (swc-info) Use correct path while getting local package versions (#​7872) (67afaf1)

Features

• (es) Add an option to disable builtin transforms (#​7873) (71d01ec)

• (es/ast) Support import attributes proposal (#​7868) (4d3fcb8)

• (es/preset-env) Update data (#​7882) (a97d8b4)

• (swc-info) Add a CLI to help issue reporting (#​7871) (d6952ea)

Miscellaneous Tasks

• (deps) Update memchr (#​7891) (01cbd6e)- general: Use textarea for swc-info (eed2903)

Performance

• (es/transforms) Remove wrong parallelism (#​7889) (a505012)

Refactor

• (es/minifier) Remove mutated and mutation_by_call_count (#​7890) (8db968a)

---

Configuration

📅 Schedule: Branch creation - "before 4am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks

[cwegrzyn]

@sgoodluck: guessing you know the most about the swc stuff and the experimental import assertions. The initial issue here is that swc renamed from keepImportAssertions to keepImportAttributes following a recent change in the ecmascript proposal. That revised proposal changes the keyword from assert to with, because you know, why not. Node/v8 doesn't support this yet, so swc also added a keyword emitAssertForImportAttributes that emits assert instead of with. However, naturally, that is broken.

I took a quick look through our code and the only apparent use of import assertions is in the one test file here. I removed the assertion usage... and it all still worked, so I think this is fine?

[sgoodluck]

Hmm, I know @nikkhn and I battled this a fair bit before. It's possible with the major updates in Node that this is no longer required. I'm inclined to accept the PR and try to deploy it to develop to see what happens. Running locally may conflict with how it behaves when building and deploying to CFP. A brief bit of googling shows some chatter on the topic.

Another related thread around ts-node.

Let's find out!

[sgoodluck]

Going to approve with the caveat that we may need to roll it back!

[cwegrzyn]

Actually, looks like they've released 1.3.84 which includes a fix for this. I'm going to close this branch and have renovate open a new one with the updated version. Can fix the config and then hopefully we'll be good to go!

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[cwegrzyn]

@nikkhn i ended up having renovate upgrade this PR rather than closing and opening a new one, so this is actually still good!

[nikkhn]

@nikkhn i ended up having renovate upgrade this PR rather than closing and opening a new one, so this is actually still good!

OH ok :D