Update @marko/compiler to 5.41.7 and marko to 5.39.27

[DylanPiercey]

Picks up @marko/compiler@5.41.7, which carries two fixes this repo needs:

• 5.41.5 shipped a dangling require("@babel/preset-typescript/package.json"), breaking the @marko/ts-plugin and marko-vscode esbuild bundles with Could not resolve "@babel/preset-typescript/package.json" (Stub the preset-typescript version read in dist/babel.js marko#3583).
• 5.41.5 and 5.41.6 published internal/babel as "type": "commonjs" over an ESM index.ts, failing tsc -b with TS1295 under verbatimModuleSyntax (Publish internal/babel as ESM, matching what it ships marko#3586).

marko moves to 5.39.27, which requires @marko/compiler ^5.41.4; the compiler range is bumped in step so only one copy is installed. Two copies make the translator read compilation state from the wrong module instance and fail with Unable to access Marko File outside of a compilation.

The changeset covers @marko/ts-plugin and marko-vscode too, since those are the packages that inline the compiler and need releases to ship fixed artifacts.

Verified: pnpm why @marko/compiler reports a single version resolving to 5.41.7, 0 TypeScript errors, all five packages build, 189 tests passing.

[changeset-bot]

🦋 Changeset detected

Latest commit: fa800fe

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@marko/language-tools	Patch
@marko/language-server	Patch
@marko/type-check	Patch
@marko/ts-plugin	Patch
marko-vscode	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 17 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7c654b0d-9f58-4fe5-8e9a-2baf223a13a9

📥 Commits

Reviewing files that changed from the base of the PR and between 9ca9161 and fa800fe.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml and included by **

📒 Files selected for processing (6)

• .changeset/bump-marko-compiler-5-41-7.md
• package.json
• packages/language-server/package.json
• packages/language-tools/package.json
• packages/ts-plugin/package.json
• packages/type-check/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dpiercey-ws-marko-ts7-k2i7kg

---

_{Comment @coderabbitai help to get the list of available commands.}