fix: avoid bundler warning for getCurrentInstance compatibility

[kazupon]

fix #2322 #2334

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/bundler-warning

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[cloudflare-workers-and-pages]

Deploying vue-i18n-next with    Cloudflare Pages

Latest commit:	d0b883b
Status:	✅  Deploy successful!
Preview URL:	https://236cf01d.vue-i18n-next.pages.dev
Branch Preview URL:	https://fix-bundler-warning.vue-i18n-next.pages.dev

View logs

[pkg-pr-new]

Open in StackBlitz

@intlify/core

npm i https://pkg.pr.new/@intlify/core@2337

@intlify/core-base

npm i https://pkg.pr.new/@intlify/core-base@2337

@intlify/devtools-types

npm i https://pkg.pr.new/@intlify/devtools-types@2337

@intlify/message-compiler

npm i https://pkg.pr.new/@intlify/message-compiler@2337

petite-vue-i18n

npm i https://pkg.pr.new/petite-vue-i18n@2337

@intlify/shared

npm i https://pkg.pr.new/@intlify/shared@2337

vue-i18n

npm i https://pkg.pr.new/vue-i18n@2337

@intlify/vue-i18n-core

npm i https://pkg.pr.new/@intlify/vue-i18n-core@2337

commit: d0b883b

[Copilot]

Pull request overview

This PR attempts to fix bundler warnings related to getCurrentInstance compatibility by modifying the approach used to access the currentInstance property from the Vue namespace. The change replaces string concatenation ('current' + 'Instance') with a constant variable (const key = 'currentInstance') to avoid bundler static analysis.

Key Changes:

• Replaced string concatenation trick with a constant variable assignment for accessing currentInstance
• Removed the inline comment explaining the bundler avoidance technique

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The new approach using const key = 'currentInstance' may not effectively avoid bundler static analysis warnings. Modern bundlers perform constant folding and can still detect this pattern. The previous string concatenation approach ('current' + 'Instance') was more effective at preventing static analysis because bundlers typically don't evaluate runtime string operations. Consider using a more robust approach such as computed property access or keeping the string concatenation method if the goal is to prevent bundler warnings.

Suggested change

	const key = 'currentInstance'
	const key = 'current' + 'Instance'