helloadhavan/github_issues huggingface dataset:
Repository: vercel/next.js
Pull request: Remove force writing **/*.mts to tsconfig

It was added at https://github.com/vercel/next.js/pull/83556. We don't force writing `**/*.tsx` or `**/*.ts` to tsconfig, but forcing `**/*.mts` is too harsh, when its intention was to support `next.config.mts`. Just for the empty tsconfig or empty include was enough.

Changed files:
filename: packages/next/src/lib/typescript/writeConfigurationDefaults.test.ts
patch: @@ -176,7 +176,7 @@ describe('writeConfigurationDefaults()', () => {
       })
 
       it('should replace includes when base is missing appTypes', async () => {
-        const include = ['**/*.ts', '**/*.tsx']
+        const include = ['**/*.ts', '**/*.tsx', '**/*.mts']
         const content = { extends: './tsconfig.base.json' }
         const baseContent = { include }
 

filename: packages/next/src/lib/typescript/writeConfigurationDefaults.ts
patch: @@ -228,9 +228,6 @@ export async function writeConfigurationDefaults(
     if (!rawConfig.include.includes(nextAppTypes)) {
       missingFromResolved.push(nextAppTypes)
     }
-    if (!rawConfig.include.includes('**/*.mts')) {
-      missingFromResolved.push('**/*.mts')
-    }
 
     if (missingFromResolved.length > 0) {
       if (!Array.isArray(userTsConfig.include)) {
Repository: nodejs/node
Pull request: meta: add mailmap entry for Aditi

Refs: https://github.com/nodejs/node/pull/59252#issuecomment-3125481270

Changed files:
filename: .mailmap
patch: @@ -6,6 +6,7 @@ Abdirahim Musse <abdirahim.musse@ibm.com> <33973272+abmusse@users.noreply.github
 Abe Fettig <abefettig@gmail.com> <abe@fettig.net>
 Abhimanyu Vashisht <abhimanyuvashisht.av@gmail.com>
 Adam Langley <agl@imperialviolet.org> <agl@google.com>
+Aditi Singh <aditisingh1400@gmail.com>
 Akhil Marsonya <akhil.marsonya27@gmail.com>
 Akhil Marsonya <akhil.marsonya27@gmail.com> <16393876+marsonya@users.noreply.github.com>
 Akito Ito <akito0107@gmail.com> <akito_ito@r.recruit.co.jp>
Repository: facebook/react
Pull request: [compiler][playground] Make change detection work in playground

Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom):
* __->__ #29889

Summary: The change detection mode was unavailable in the playground because the pragma was not a boolean. This fixes that by special casing it in pragma parsing, similar to validateNoCapitalizedCalls

Changed files:
filename: compiler/packages/babel-plugin-react-compiler/src/HIR/Environment.ts
patch: @@ -410,6 +410,17 @@ export function parseConfigPragma(pragma: string): EnvironmentConfig {
       continue;
     }
 
+    if (
+      key === "enableChangeDetectionForDebugging" &&
+      (val === undefined || val === "true")
+    ) {
+      maybeConfig[key] = {
+        source: "react-compiler-runtime",
+        importSpecifierName: "$structuralCheck",
+      };
+      continue;
+    }
+
     if (typeof defaultConfig[key as keyof EnvironmentConfig] !== "boolean") {
       // skip parsing non-boolean properties
       continue;
Repository: ollama/ollama
Pull request: Add twinny vscode extension to Extensions and Plugins

Hey, thanks for the awesome work you've been doing with Ollama.

I was hoping that you would consider adding my extension for vscode to the list of extensions and plugins for Ollama.  

It's basically a Copilot alternative with FIM and Chat features.

https://github.com/rjmacarthy/twinny

Many thanks,

Richard

Changed files:
filename: README.md
patch: @@ -327,3 +327,5 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Llama Coder](https://github.com/ex3ndr/llama-coder) (Copilot alternative using Ollama)
 - [Obsidian BMO Chatbot plugin](https://github.com/longy2k/obsidian-bmo-chatbot)
 - [Open Interpreter](https://docs.openinterpreter.com/language-model-setup/local-models/ollama)
+- [twinny](https://github.com/rjmacarthy/twinny) (Copilot and Copilot chat alternative using Ollama)
+
Repository: facebook/react
Pull request: [compiler] Fix visitors to emit the correct kind

Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom):
* __->__ #29884

Our passes aren't sequenced such that we could observe this bug, but this retains the proper terminal kind for pruned-scopes in mapTerminalSuccessors.

Changed files:
filename: compiler/packages/babel-plugin-react-compiler/src/HIR/visitors.ts
patch: @@ -856,7 +856,7 @@ export function mapTerminalSuccessors(
       const block = fn(terminal.block);
       const fallthrough = fn(terminal.fallthrough);
       return {
-        kind: "scope",
+        kind: terminal.kind,
         scope: terminal.scope,
         block,
         fallthrough,
Repository: vercel/next.js
Pull request: Add Descope to Auth libraries list

Add Descope to Auth libraries list as mentioned [here](https://github.com/vercel/next.js/pull/75667#issuecomment-3309812276)

Changed files:
filename: docs/01-app/02-guides/authentication.mdx
patch: @@ -1627,6 +1627,7 @@ Now that you've learned about authentication in Next.js, here are Next.js-compat
 - [Auth0](https://auth0.com/docs/quickstart/webapp/nextjs/01-login)
 - [Better Auth](https://www.better-auth.com/docs/integrations/next)
 - [Clerk](https://clerk.com/docs/quickstarts/nextjs)
+- [Descope](https://docs.descope.com/getting-started/nextjs)
 - [Kinde](https://kinde.com/docs/developer-tools/nextjs-sdk)
 - [Logto](https://docs.logto.io/quick-starts/next-app-router)
 - [NextAuth.js](https://authjs.dev/getting-started/installation?framework=next.js)
Repository: nodejs/node
Pull request: doc: correct orthography `eg.` → `e.g.`

"exempli gratia" is abbreviated "e.g."

Changed files:
filename: doc/contributing/investigating-native-memory-leaks.md
patch: @@ -396,7 +396,7 @@ call:
 }
 ```
 
-Create a file (eg. `node-12.14.1.supp`) with the contents of the suppression
+Create a file (e.g. `node-12.14.1.supp`) with the contents of the suppression
 records, and run Valgrind with the suppression file previously created:
 
 ```bash

filename: tools/msvs/msi/nodemsi/product.wxs
patch: @@ -41,7 +41,7 @@
     <Property Id="WIXUI_INSTALLDIR" Value="INSTALLDIR"/>
 
     <!-- WiX 4 QueryWindowsWellKnownSIDs element replaces previously used PropertyRef. -->
-    <!-- It sets all properties with the WIX_ACCOUNT_ prefix eg. WIX_ACCOUNT_USERS, etc. -->
+    <!-- It sets all properties with the WIX_ACCOUNT_ prefix e.g. WIX_ACCOUNT_USERS, etc. -->
     <util:QueryWindowsWellKnownSIDs/>
 
     <Property Id="INSTALLDIR" Secure="yes">
Repository: huggingface/transformers
Pull request: Revert change in `compile_friendly_resize`

# What does this PR do?

Reverts https://github.com/huggingface/transformers/pull/40436 and adds comments to avoid regression

cc @remi-or @yonigozlan 

Changed files:
filename: src/transformers/image_processing_utils_fast.py
patch: @@ -375,9 +375,13 @@ def compile_friendly_resize(
         A wrapper around `F.resize` so that it is compatible with torch.compile when the image is a uint8 tensor.
         """
         if image.dtype == torch.uint8:
-            image = image.float() / 255
+            # 256 is used on purpose instead of 255 to avoid numerical differences
+            # see https://github.com/huggingface/transformers/pull/38540#discussion_r2127165652
+            image = image.float() / 256
             image = F.resize(image, new_size, interpolation=interpolation, antialias=antialias)
-            image = image * 255
+            image = image * 256
+            # torch.where is used on purpose instead of torch.clamp to avoid bug in torch.compile
+            # see https://github.com/huggingface/transformers/pull/38540#discussion_r2126888471
             image = torch.where(image > 255, 255, image)
             image = torch.where(image < 0, 0, image)
             image = image.round().to(torch.uint8)
Repository: electron/electron
Pull request: feat: add support for `--experimental-network-inspection`

Backport of #46690

See that PR for details.


Notes: Added support for node option `--experimental-network-inspection`


Changed files:
filename: docs/api/command-line-switches.md
patch: @@ -254,7 +254,7 @@ Electron supports some of the [CLI flags][node-cli] supported by Node.js.
 
 **Note:** Passing unsupported command line switches to Electron when it is not running in `ELECTRON_RUN_AS_NODE` will have no effect.
 
-### `--inspect-brk\[=\[host:]port]`
+### `--inspect-brk[=[host:]port]`
 
 Activate inspector on host:port and break at start of user script. Default host:port is 127.0.0.1:9229.
 
@@ -266,13 +266,13 @@ Activate inspector on `host:port` and break at start of the first internal
 JavaScript script executed when the inspector is available.
 Default `host:port` is `127.0.0.1:9229`.
 
-### `--inspect-port=\[host:]port`
+### `--inspect-port=[host:]port`
 
 Set the `host:port` to be used when the inspector is activated. Useful when activating the inspector by sending the SIGUSR1 signal. Default host is `127.0.0.1`.
 
 Aliased to `--debug-port=[host:]port`.
 
-### `--inspect\[=\[host:]port]`
+### `--inspect[=[host:]port]`
 
 Activate inspector on `host:port`. Default is `127.0.0.1:9229`.
 
@@ -288,6 +288,10 @@ Specify ways of the inspector web socket url exposure.
 
 By default inspector websocket url is available in stderr and under /json/list endpoint on `http://host:port/json/list`.
 
+### `--experimental-network-inspector`
+
+Enable support for devtools network inspector events, for visibility into requests made by the nodejs `http` and `https` modules.
+
 ### `--no-deprecation`
 
 Silence deprecation warnings.

filename: shell/common/node_bindings.cc
patch: @@ -348,6 +348,7 @@ bool IsAllowedOption(const std::string_view option) {
           "--inspect-brk-node",
           "--inspect-port",
           "--inspect-publish-uid",
+          "--experimental-network-inspection",
       });
 
   // This should be aligned with what's possible to set via the process object.
Repository: ollama/ollama
Pull request: Added - [Ollama for R - rollama] in README.md

Added - [Ollama for R - rollama](https://github.com/JBGruber/rollama) in Libraries in README.md

Changed files:
filename: README.md
patch: @@ -304,6 +304,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [LangChainDart](https://github.com/davidmigloz/langchain_dart)
 - [Semantic Kernel - Python](https://github.com/microsoft/semantic-kernel/tree/main/python/semantic_kernel/connectors/ai/ollama)
 - [Haystack](https://github.com/deepset-ai/haystack-integrations/blob/main/integrations/ollama.md)
+- [Ollama for R - rollama](https://github.com/JBGruber/rollama)
 
 
 ### Mobile
Repository: denoland/deno
Pull request: fix(ext/node): emit deprecation warning for SlowBuffer

Adds the DEP0030 deprecation warning when SlowBuffer() is called, matching Node.js behavior. 
This fixes the node_compat test parallel/test-buffer-slow.js.

Changed files:
filename: ext/node/polyfills/internal/buffer.mjs
patch: @@ -153,10 +153,13 @@ export const constants = {
 };
 
 let bufferWarningAlreadyEmitted = false;
+let slowBufferWarningAlreadyEmitted = false;
 let nodeModulesCheckCounter = 0;
 const bufferWarning = "Buffer() is deprecated due to security and usability " +
   "issues. Please use the Buffer.alloc(), " +
   "Buffer.allocUnsafe(), or Buffer.from() methods instead.";
+const slowBufferWarning =
+  "SlowBuffer() is deprecated. Please use Buffer.allocUnsafeSlow()";
 
 function showFlaggedDeprecation() {
   if (
@@ -514,6 +517,10 @@ function checked(length) {
 }
 
 export function SlowBuffer(length) {
+  if (!slowBufferWarningAlreadyEmitted) {
+    slowBufferWarningAlreadyEmitted = true;
+    process.emitWarning(slowBufferWarning, "DeprecationWarning", "DEP0030");
+  }
   assertSize(length);
   return _alloc(+length);
 }

filename: tests/node_compat/config.json
patch: @@ -130,6 +130,7 @@
     "parallel/test-buffer-set-inspect-max-bytes.js": {},
     "parallel/test-buffer-sharedarraybuffer.js": {},
     "parallel/test-buffer-slice.js": {},
+    "parallel/test-buffer-slow.js": {},
     "parallel/test-buffer-swap.js": {},
     "parallel/test-buffer-tojson.js": {},
     "parallel/test-buffer-tostring-range.js": {},
Repository: huggingface/transformers
Pull request: Fix Issue #39030: AutoTokenizer.from_pretrained does not propagate token

# What does this PR do?

Fixes #39030. Propagates token through `list_repo_templates` to `list_repo_tree`.


## Who can review?

@ArthurZucker @Rocketknight1 

Changed files:
filename: src/transformers/processing_utils.py
patch: @@ -963,6 +963,7 @@ def get_processor_dict(
                         local_files_only=local_files_only,
                         revision=revision,
                         cache_dir=cache_dir,
+                        token=token,
                     ):
                         additional_chat_template_files[template] = f"{CHAT_TEMPLATE_DIR}/{template}.jinja"
                 except EntryNotFoundError:

filename: src/transformers/tokenization_utils_base.py
patch: @@ -2042,6 +2042,7 @@ def from_pretrained(
                             local_files_only=local_files_only,
                             revision=revision,
                             cache_dir=cache_dir,
+                            token=token,
                         ):
                             template = template.removesuffix(".jinja")
                             vocab_files[f"chat_template_{template}"] = f"{CHAT_TEMPLATE_DIR}/{template}.jinja"

filename: src/transformers/utils/hub.py
patch: @@ -155,6 +155,7 @@ def list_repo_templates(
     local_files_only: bool,
     revision: Optional[str] = None,
     cache_dir: Optional[str] = None,
+    token: Union[bool, str, None] = None,
 ) -> list[str]:
     """List template files from a repo.
 
@@ -171,6 +172,7 @@ def list_repo_templates(
                     revision=revision,
                     path_in_repo=CHAT_TEMPLATE_DIR,
                     recursive=False,
+                    token=token,
                 )
                 if entry.path.endswith(".jinja")
             ]
Repository: electron/electron
Pull request: feat: add support for `--experimental-network-inspection`

Backport of #46690

See that PR for details.


Notes: Added support for node option `--experimental-network-inspection`


Changed files:
filename: docs/api/command-line-switches.md
patch: @@ -256,7 +256,7 @@ Electron supports some of the [CLI flags][node-cli] supported by Node.js.
 > [!NOTE]
 > Passing unsupported command line switches to Electron when it is not running in `ELECTRON_RUN_AS_NODE` will have no effect.
 
-### `--inspect-brk\[=\[host:]port]`
+### `--inspect-brk[=[host:]port]`
 
 Activate inspector on host:port and break at start of user script. Default host:port is 127.0.0.1:9229.
 
@@ -268,13 +268,13 @@ Activate inspector on `host:port` and break at start of the first internal
 JavaScript script executed when the inspector is available.
 Default `host:port` is `127.0.0.1:9229`.
 
-### `--inspect-port=\[host:]port`
+### `--inspect-port=[host:]port`
 
 Set the `host:port` to be used when the inspector is activated. Useful when activating the inspector by sending the SIGUSR1 signal. Default host is `127.0.0.1`.
 
 Aliased to `--debug-port=[host:]port`.
 
-### `--inspect\[=\[host:]port]`
+### `--inspect[=[host:]port]`
 
 Activate inspector on `host:port`. Default is `127.0.0.1:9229`.
 
@@ -290,6 +290,10 @@ Specify ways of the inspector web socket url exposure.
 
 By default inspector websocket url is available in stderr and under /json/list endpoint on `http://host:port/json/list`.
 
+### `--experimental-network-inspector`
+
+Enable support for devtools network inspector events, for visibility into requests made by the nodejs `http` and `https` modules.
+
 ### `--no-deprecation`
 
 Silence deprecation warnings.

filename: shell/common/node_bindings.cc
patch: @@ -348,6 +348,7 @@ bool IsAllowedOption(const std::string_view option) {
           "--inspect-brk-node",
           "--inspect-port",
           "--inspect-publish-uid",
+          "--experimental-network-inspection",
       });
 
   // This should be aligned with what's possible to set via the process object.
Repository: nodejs/node
Pull request: doc: clarify the need of compiler compatible with c++20

Very often, someone appears in the #node-core slack channel asking for guidance on this compilation error


Changed files:
filename: BUILDING.md
patch: @@ -272,6 +272,11 @@ export CXX=g++-12
 make -j4
 ```
 
+> \[!IMPORTANT]
+> If you face a compilation error during this process such as
+> `error: no matching conversion for functional-style cast from 'unsigned int' to 'TypeIndex'`
+> Make sure to use a `g++` or `clang` version compatible with C++20.
+
 We can speed up the builds by using [Ninja](https://ninja-build.org/). For more
 information, see
 [Building Node.js with Ninja](doc/contributing/building-node-with-ninja.md).
Repository: ollama/ollama
Pull request: Add container hints for troubleshooting

Some users are new to containers and unsure where the server logs go

Changed files:
filename: docs/troubleshooting.md
patch: @@ -12,6 +12,13 @@ On Linux systems with systemd, the logs can be found with this command:
 journalctl -u ollama
 ```
 
+When you run Ollama in a container, the logs go to stdout/stderr in the container:
+
+```shell
+docker logs <container-name>
+```
+(Use `docker ps` to find the container name)
+
 If manually running `ollama serve` in a terminal, the logs will be on that terminal.
 
 Join the [Discord](https://discord.gg/ollama) for help interpreting the logs.
Repository: electron/electron
Pull request: feat: enable secondary label for macOS menu

Backport of #46887

See that PR for details.


Notes: added sublabel functionality for menus on macOS >= 14.4


Changed files:
filename: docs/api/menu-item.md
patch: @@ -19,7 +19,7 @@ See [`Menu`](menu.md) for examples.
   * `type` string (optional) - Can be `normal`, `separator`, `submenu`, `checkbox` or
     `radio`.
   * `label` string (optional)
-  * `sublabel` string (optional)
+  * `sublabel` string (optional) _macOS_ - Available in macOS >= 14.4
   * `toolTip` string (optional) _macOS_ - Hover text for this menu item.
   * `accelerator` [Accelerator](accelerator.md) (optional)
   * `icon` ([NativeImage](native-image.md) | string) (optional)

filename: docs/api/menu.md
patch: @@ -332,6 +332,27 @@ name, no matter what label you set. To change it, modify your app bundle's
 [About Information Property List Files][AboutInformationPropertyListFiles]
 for more information.
 
+### Menu Sublabels
+
+Menu sublabels, or [subtitles](https://developer.apple.com/documentation/appkit/nsmenuitem/subtitle?language=objc), can be added to menu items using the `sublabel` option. Below is an example based on the renderer example above:
+
+```js @ts-expect-error=[12]
+// main
+ipcMain.on('show-context-menu', (event) => {
+  const template = [
+    {
+      label: 'Menu Item 1',
+      sublabel: 'Subtitle 1',
+      click: () => { event.sender.send('context-menu-command', 'menu-item-1') }
+    },
+    { type: 'separator' },
+    { label: 'Menu Item 2', sublabel: 'Subtitle 2', type: 'checkbox', checked: true }
+  ]
+  const menu = Menu.buildFromTemplate(template)
+  menu.popup({ window: BrowserWindow.fromWebContents(event.sender) })
+})
+```
+
 ## Setting Menu for Specific Browser Window (_Linux_ _Windows_)
 
 The [`setMenu` method][setMenu] of browser windows can set the menu of certain

filename: shell/browser/ui/cocoa/electron_menu_controller.mm
patch: @@ -315,12 +315,21 @@ - (NSMenuItem*)menuItemForService:(NSSharingService*)service
 - (NSMenuItem*)makeMenuItemForIndex:(NSInteger)index
                           fromModel:(electron::ElectronMenuModel*)model {
   std::u16string label16 = model->GetLabelAt(index);
+  auto rawSecondaryLabel = model->GetSecondaryLabelAt(index);
   NSString* label = l10n_util::FixUpWindowsStyleLabel(label16);
 
   NSMenuItem* item = [[NSMenuItem alloc] initWithTitle:label
                                                 action:@selector(itemSelected:)
                                          keyEquivalent:@""];
 
+  if (!rawSecondaryLabel.empty()) {
+    if (@available(macOS 14.4, *)) {
+      NSString* secondary_label =
+          l10n_util::FixUpWindowsStyleLabel(rawSecondaryLabel);
+      item.subtitle = secondary_label;
+    }
+  }
+
   // If the menu item has an icon, set it.
   ui::ImageModel icon = model->GetIconAt(index);
   if (icon.IsImage())
Repository: ollama/ollama
Pull request: Don't disable GPUs on arm without AVX

AVX is an x86 feature, so ARM should be excluded from the check.

Related to #1979 

Changed files:
filename: gpu/gpu.go
patch: @@ -122,15 +122,15 @@ func GetGPUInfo() GpuInfo {
 		initGPUHandles()
 	}
 
-	// All our GPU builds have AVX enabled, so fallback to CPU if we don't detect at least AVX
+	// All our GPU builds on x86 have AVX enabled, so fallback to CPU if we don't detect at least AVX
 	cpuVariant := GetCPUVariant()
-	if cpuVariant == "" {
+	if cpuVariant == "" && runtime.GOARCH == "amd64" {
 		slog.Warn("CPU does not have AVX or AVX2, disabling GPU support.")
 	}
 
 	var memInfo C.mem_info_t
 	resp := GpuInfo{}
-	if gpuHandles.cuda != nil && cpuVariant != "" {
+	if gpuHandles.cuda != nil && (cpuVariant != "" || runtime.GOARCH != "amd64") {
 		C.cuda_check_vram(*gpuHandles.cuda, &memInfo)
 		if memInfo.err != nil {
 			slog.Info(fmt.Sprintf("error looking up CUDA GPU memory: %s", C.GoString(memInfo.err)))
@@ -149,7 +149,7 @@ func GetGPUInfo() GpuInfo {
 				slog.Info(fmt.Sprintf("CUDA GPU is too old. Falling back to CPU mode. Compute Capability detected: %d.%d", cc.major, cc.minor))
 			}
 		}
-	} else if gpuHandles.rocm != nil && cpuVariant != "" {
+	} else if gpuHandles.rocm != nil && (cpuVariant != "" || runtime.GOARCH != "amd64") {
 		C.rocm_check_vram(*gpuHandles.rocm, &memInfo)
 		if memInfo.err != nil {
 			slog.Info(fmt.Sprintf("error looking up ROCm GPU memory: %s", C.GoString(memInfo.err)))
Repository: ollama/ollama
Pull request: Log prompt when running `ollama serve` with `OLLAMA_DEBUG=1`

Fixes https://github.com/ollama/ollama/issues/1533
Fixes https://github.com/ollama/ollama/issues/1118


Changed files:
filename: server/routes.go
patch: @@ -253,6 +253,8 @@ func GenerateHandler(c *gin.Context) {
 		prompt = rebuild.String()
 	}
 
+	slog.Debug(fmt.Sprintf("prompt: %s", prompt))
+
 	ch := make(chan any)
 	var generated strings.Builder
 	go func() {
@@ -1125,6 +1127,8 @@ func ChatHandler(c *gin.Context) {
 		return
 	}
 
+	slog.Debug(fmt.Sprintf("prompt: %s", prompt))
+
 	ch := make(chan any)
 
 	go func() {
Repository: facebook/react
Pull request: Standardize condition order so that edge-lite preferred over browser

The export maps for react packages have to choose an order of preference. Many runtimes use multiple conditions, for instance when building for edge webpack also uses the browser condition which makes sense given most edge runtimes have a web-standards based set of APIs. However React is building the browser builds primarily for actual browsers and sometimes have builds intended for servers that might be browser compat. This change updates the order of conditions to preference specific named runtimes > node > generic edge runtimes > browser > default



Changed files:
filename: packages/react-dom/package.json
patch: @@ -63,9 +63,9 @@
       "bun": "./server.bun.js",
       "deno": "./server.browser.js",
       "worker": "./server.browser.js",
-      "browser": "./server.browser.js",
       "node": "./server.node.js",
       "edge-light": "./server.edge.js",
+      "browser": "./server.browser.js",
       "default": "./server.node.js"
     },
     "./server.browser": {
@@ -89,9 +89,9 @@
       "workerd": "./static.edge.js",
       "deno": "./static.browser.js",
       "worker": "./static.browser.js",
-      "browser": "./static.browser.js",
       "node": "./static.node.js",
       "edge-light": "./static.edge.js",
+      "browser": "./static.browser.js",
       "default": "./static.node.js"
     },
     "./static.browser": {