wxt-dev/wxt

Config to specify IIFE name or disable it altogether

Open

#2,004 建立於 2025年12月16日

在 GitHub 查看
 (4 留言) (0 反應) (1 負責人)TypeScript (9,861 star) (511 fork)user submission
contribution welcomegood first issue

描述

Before that, I want to run an alternative by you: would it make more sense to add this to defineContentScript (as an option like cssInjectionMode, matches, etc) instead of wxt.config.ts?

export default defineContentScript({
  iffeName: "example",
  // OR `globalName: string | boolean`, letting people disable the iffe name in the  output as well as give it a different name.

  main() {
    // ...
  }
})

In this version, it would default to true and the name would be generated based on the content script name, but in the next major version would could change the default to false so a name isn't even generated in the first place.

— Originally posted by @aklinker1 in https://github.com/wxt-dev/wxt/pull/1897#pullrequestreview-3385640996

貢獻者指南

技術棧
typescript
領域
frontenddeveloper experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
TypeScript basicsWXT content script APIIIFE concept
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Review the current implementation of `defineContentScript` in the WXT framework (likely in packages/wxt/src/...). Understand how content script options are processed and how the IIFE name is generated during the build. Look at the linked PR #1897 discussion for context. Determine the best approach to add an `iffeName` or `globalName` option to the configuration.