Weekly Update, April 16, 2025 – Faster Bundle Times with 3.3-beta.0! 🚀

[nachocodoner]

@ferjep

SyntaxError: await is only valid in async functions and the top level bodies of modules

Mmm, seems like there’s an issue with top-level await in browser-policy-content package. Oddly, it doesn’t fall back to Babel automatically.

What happens if you try this config?

"meteor": {
    "modernWebArchsOnly": true,
    "modernTranspiler": {
       "excludePackages": ["browser-policy-content"]
    },
    "mainModule": {
      "client": "client/main.js",
      "server": "server/main.js"
    }
  },

This is just a quick test. I’ll check into it, it should support top-level await (TLA) since we keep reify on SWC compilation, and webapp package, which also uses TLA works well with SWC.

---

Update: I reproduced the issue and confirm the config above solves it.

However, I found the proper fix in SWC’s code transpilation. It will be included in the upcoming 3.3-beta.1. At that time, you could remove the “excludePackages” config.

Favor Reify transpile in SWC all time

Thanks for the report. These are essential for stable delivery.

[italojs]

[UPDATE]
SOLVED: Error when observing the cursor: TypeError: this.documents?.clear is not a function

Error when observing the cursor: TypeError: this.documents?.clear is not a function

[harry97]

- YouTube

[minhna]

[wreiske]

I’ve been using 3.3-beta.0 this weekend. The biggest thing that is annoying me during development is it doesn’t seem to know how to get to the code like the old bundler. Everything is anon both client and serverside.

  "meteor": {
    "modernWebArchsOnly": true,
    "modernTranspiler": true,
    "mainModule": {
      "client": "client/main.js",
      "server": "server/main.js"
    },
    "testModule": "tests/main.js"
  },

This also makes using debugger impossible.

[nachocodoner]

Thanks for testing. This time it’s a common use case we haven’t test so much yet, debugging.

I believe the issue is related to how we link the source map data with the file metadata in SWC. I will review this use case, as it likely misses the proper configuration.