helloadhavan/github_issues huggingface dataset:
Repository: electron/electron
Pull request: build: ask bug reporters to check if it is a Chromium issue

#### Description of Change

<!--
Thank you for your Pull Request. Please provide a description above and review
the requirements below.

Contributors guide: https://github.com/electron/electron/blob/main/CONTRIBUTING.md
-->

We've been seeing a lot of Chromium issues reported in our bug tracker recently.

Thanks to @KAGEYAM4 for suggesting this in [this comment](https://github.com/electron/electron/issues/47672#issuecomment-3051298922).

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [x] PR description included and stakeholders cc'd
- [x] [PR release notes](https://github.com/electron/clerk/blob/main/README.md) describe the change in a way relevant to app developers, and are [capitalized, punctuated, and past tense](https://github.com/electron/clerk/blob/main/README.md#examples).

#### Release Notes

Notes: none


Changed files:
filename: .github/ISSUE_TEMPLATE/bug_report.yml
patch: @@ -58,6 +58,15 @@ body:
     label: Last Known Working Electron version
     description: What is the last version of Electron this worked in, if applicable?
     placeholder: 16.0.0
+- type: dropdown
+  attributes:
+    label: Does the issue also appear in Chromium / Google Chrome?
+    description: If it does, please report the issue in the [Chromium issue tracker](https://issues.chromium.org/issues), not against Electron. Electron will inherit the fix once Chromium resolves the issue.
+    options:
+      - "Yes"
+      - "No"
+  validations:
+    required: true
 - type: textarea
   attributes:
     label: Expected Behavior
Repository: facebook/react
Pull request: [ez] Add @noformat etc headers into some files

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

These are only needed internally so I'm opting to just do it in the
commit artifacts job instead of amending the build config.

Changed files:
filename: .github/workflows/runtime_commit_artifacts.yml
patch: @@ -85,6 +85,11 @@ jobs:
           sed -i -e 's/ @license React*//' \
             build/oss-experimental/eslint-plugin-react-hooks/cjs/eslint-plugin-react-hooks.development.js \
             build/oss-experimental/react-refresh/cjs/react-refresh-babel.development.js
+      - name: Insert @headers into eslint plugin and react-refresh
+        run: |
+          sed -i -e 's/ LICENSE file in the root directory of this source tree./ LICENSE file in the root directory of this source tree.\n * \n * @noformat\n * @nolint\n * @lightSyntaxTransform\n * @preventMunge\n * @oncall react_core/' \
+            build/oss-experimental/eslint-plugin-react-hooks/cjs/eslint-plugin-react-hooks.development.js \
+            build/oss-experimental/react-refresh/cjs/react-refresh-babel.development.js
       - name: Move relevant files for React in www into compiled
         run: |
           # Move the facebook-www folder into compiled
Repository: ollama/ollama
Pull request: Fix copying model to itself


Changed files:
filename: server/images.go
patch: @@ -710,6 +710,10 @@ func CopyModel(src, dst model.Name) error {
 		return model.Unqualified(src)
 	}
 
+	if src.Filepath() == dst.Filepath() {
+		return nil
+	}
+
 	manifests, err := GetManifestPath()
 	if err != nil {
 		return err
Repository: vercel/next.js
Pull request: [turbopack] No op the webpack bundle analyzer under turbopack

This never worked with turbopack, but with the recent default flip using this now breaks the build since it complains about configuring webpack in a turbopack build.

So print a warning and no-op the analyzer.  This isn't ideal but it is more actionable than a crash for users.

Closes PACK-5653

Changed files:
filename: packages/next-bundle-analyzer/index.js
patch: @@ -4,6 +4,13 @@ module.exports =
     if (!enabled) {
       return nextConfig
     }
+    if (process.env.TURBOPACK) {
+      console.warn(
+        'The Next Bundle Analyzer is not compatible with Turbopack builds yet, no report will be generated.\n\n' +
+          'To run this analysis pass the `--webpack` flag to `next build`'
+      )
+      return nextConfig
+    }
 
     const extension = analyzerMode === 'json' ? '.json' : '.html'
Repository: facebook/react
Pull request: [Fizz] use microtasks rather than tasks when scheduling work while prerendering

Similar to https://github.com/facebook/react/pull/30768 we want to schedule work during prerendering in microtasks both for the root task and pings. We continue to schedule flushes as Tasks to allow as much work to be batched up as possible.


Changed files:
filename: packages/react-server/src/ReactFizzServer.js
patch: @@ -38,6 +38,7 @@ import {describeObjectForErrorMessage} from 'shared/ReactSerializationErrors';
 
 import {
   scheduleWork,
+  scheduleMicrotask,
   beginWriting,
   writeChunk,
   writeChunkAndReturn,
@@ -669,7 +670,11 @@ function pingTask(request: Request, task: Task): void {
   pingedTasks.push(task);
   if (request.pingedTasks.length === 1) {
     request.flushScheduled = request.destination !== null;
-    scheduleWork(() => performWork(request));
+    if (request.trackedPostpones !== null) {
+      scheduleMicrotask(() => performWork(request));
+    } else {
+      scheduleWork(() => performWork(request));
+    }
   }
 }
 
@@ -4893,12 +4898,22 @@ function flushCompletedQueues(
 
 export function startWork(request: Request): void {
   request.flushScheduled = request.destination !== null;
-  if (supportsRequestStorage) {
-    scheduleWork(() => requestStorage.run(request, performWork, request));
+  if (request.trackedPostpones !== null) {
+    // When prerendering we use microtasks for pinging work
+    if (supportsRequestStorage) {
+      scheduleMicrotask(() =>
+        requestStorage.run(request, performWork, request),
+      );
+    } else {
+      scheduleMicrotask(() => performWork(request));
+    }
   } else {
-    scheduleWork(() => performWork(request));
-  }
-  if (request.trackedPostpones === null) {
+    // When rendering/resuming we use regular tasks and we also emit early preloads
+    if (supportsRequestStorage) {
+      scheduleWork(() => requestStorage.run(request, performWork, request));
+    } else {
+      scheduleWork(() => performWork(request));
+    }
     // this is either a regular render or a resume. For regular render we want
     // to call emitEarlyPreloads after the first performWork because we want
     // are responding to a live request and need to balance sending something early
Repository: nodejs/node
Pull request: test: skip more sea tests on Linux ppc64le

Theses tests are failing when compiled with clang. Skip for now to avoid breaking the CI when we switch over to building with clang.

Refs: https://github.com/nodejs/node/issues/59561

<!--
Before submitting a pull request, please read:

- the CONTRIBUTING guide at https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md
- the commit message formatting guidelines at
  https://github.com/nodejs/node/blob/HEAD/doc/contributing/pull-requests.md#commit-message-guidelines

For code changes:
1. Include tests for any bug fixes or new features.
2. Update documentation if relevant.
3. Ensure that `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes.

If you believe this PR should be highlighted in the Node.js CHANGELOG
please add the `notable-change` label.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.
-->


Changed files:
filename: test/sequential/sequential.status
patch: @@ -63,6 +63,9 @@ test-single-executable-application-disable-experimental-sea-warning: SKIP
 test-single-executable-application-empty: SKIP
 test-single-executable-application-exec-argv: SKIP
 test-single-executable-application-exec-argv-empty: SKIP
+test-single-executable-application-exec-argv-extension-cli: SKIP
+test-single-executable-application-exec-argv-extension-env: SKIP
+test-single-executable-application-exec-argv-extension-none: SKIP
 test-single-executable-application-inspect-in-sea-flags: SKIP
 test-single-executable-application-inspect: SKIP
 test-single-executable-application-snapshot: SKIP
Repository: denoland/deno
Pull request: fix(ext/node): emit correct error codes for unsupported PQC key types

## Summary
- When `createPublicKey` or `createPrivateKey` encounters an unsupported PQC key type (ML-KEM, ML-DSA, SLH-DSA), emit Node-compatible error codes (`ERR_OSSL_EVP_DECODE_ERROR` / `ERR_OSSL_UNSUPPORTED`) instead of a plain TypeError without a `code` property
- Enables 3 node_compat tests: `test-crypto-pqc-key-objects-{ml-dsa,ml-kem,slh-dsa}`

## Test plan
- [x] `cargo test --test node_compat -- test-crypto-pqc-key-objects-` passes (3/3 tests)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Changed files:
filename: ext/node_crypto/keys.rs
patch: @@ -611,6 +611,12 @@ pub enum EdRawError {
   UnsupportedCurve,
 }
 
+#[derive(Debug, thiserror::Error, deno_error::JsError)]
+#[class(generic)]
+#[error("unsupported")]
+#[property("code" = "ERR_OSSL_UNSUPPORTED")]
+pub struct UnsupportedPrivateKeyOidError;
+
 #[derive(Debug, thiserror::Error, deno_error::JsError)]
 #[class(type)]
 pub enum AsymmetricPrivateKeyError {
@@ -669,8 +675,13 @@ pub enum AsymmetricPrivateKeyError {
   InvalidEd448PrivateKey,
   #[error("missing dh parameters")]
   MissingDhParameters,
-  #[error("unsupported private key oid")]
-  UnsupportedPrivateKeyOid,
+  #[class(inherit)]
+  #[error(transparent)]
+  UnsupportedPrivateKeyOid(
+    #[from]
+    #[inherit]
+    UnsupportedPrivateKeyOidError,
+  ),
 }
 
 #[derive(Debug, thiserror::Error, deno_error::JsError)]
@@ -771,8 +782,9 @@ pub enum AsymmetricPublicKeyError {
   #[class(type)]
   #[error("malformed or missing public key in dh spki")]
   MalformedOrMissingPublicKeyInDhSpki,
-  #[class(type)]
-  #[error("unsupported private key oid")]
+  #[class(generic)]
+  #[error("unsupported")]
+  #[property("code" = "ERR_OSSL_EVP_DECODE_ERROR")]
   UnsupportedPrivateKeyOid,
 }
 
@@ -998,7 +1010,7 @@ impl KeyObjectHandle {
           params,
         })
       }
-      _ => return Err(AsymmetricPrivateKeyError::UnsupportedPrivateKeyOid),
+      _ => return Err(UnsupportedPrivateKeyOidError.into()),
     };
 
     Ok(KeyObjectHandle::AsymmetricPrivate(private_key))

filename: tests/node_compat/config.jsonc
patch: @@ -301,6 +301,9 @@
     "parallel/test-crypto-oneshot-hash.js": {},
     "parallel/test-crypto-op-during-process-exit.js": {},
     "parallel/test-crypto-padding-aes256.js": {},
+    "parallel/test-crypto-pqc-key-objects-ml-dsa.js": {},
+    "parallel/test-crypto-pqc-key-objects-ml-kem.js": {},
+    "parallel/test-crypto-pqc-key-objects-slh-dsa.js": {},
     "parallel/test-crypto-psychic-signatures.js": {},
     "parallel/test-crypto-randomfillsync-regression.js": {},
     "parallel/test-crypto-randomuuid.js": {},
Repository: ggml-org/llama.cpp
Pull request: webui: fix chat header width when sidebar is closed

This fixes a small issue where the chat header was not resized to fill the screen width when collapsing the sidebar manually. I also copied the transition style `duration-200 ease-linear` from the sidebar button to match the animation.

<img width="1088" height="529" alt="collapsed-before-after" src="https://github.com/user-attachments/assets/b344d9f0-c7b2-4c1a-92ca-cd0728e0a57a" />


Changed files:
filename: tools/server/webui/src/lib/components/app/chat/ChatScreen/ChatScreenHeader.svelte
patch: @@ -2,6 +2,9 @@
 	import { Settings } from '@lucide/svelte';
 	import { DialogChatSettings } from '$lib/components/app';
 	import { Button } from '$lib/components/ui/button';
+	import { useSidebar } from '$lib/components/ui/sidebar';
+
+	const sidebar = useSidebar();
 
 	let settingsOpen = $state(false);
 
@@ -11,7 +14,9 @@
 </script>
 
 <header
-	class="md:background-transparent pointer-events-none fixed top-0 right-0 left-0 z-50 flex items-center justify-end bg-background/40 p-4 backdrop-blur-xl md:left-[var(--sidebar-width)]"
+	class="md:background-transparent pointer-events-none fixed top-0 right-0 left-0 z-50 flex items-center justify-end bg-background/40 p-4 backdrop-blur-xl duration-200 ease-linear {sidebar.open
+		? 'md:left-[var(--sidebar-width)]'
+		: ''}"
 >
 	<div class="pointer-events-auto flex items-center space-x-2">
 		<Button variant="ghost" size="sm" onclick={toggleSettings}>
Repository: nodejs/node
Pull request: meta: bump `codecov/codecov-action` to 5.5.0

Refs: https://github.com/codecov/codecov-action/commit/fdcc8476540edceab3de004e990f80d881c6cc00

Changed files:
filename: .github/workflows/coverage-linux-without-intl.yml
patch: @@ -84,6 +84,6 @@ jobs:
       - name: Clean tmp
         run: rm -rf coverage/tmp && rm -rf out
       - name: Upload
-        uses: codecov/codecov-action@39a2af19d997be74586469d4062e173ecae614f6  # v5.4.3+
+        uses: codecov/codecov-action@fdcc8476540edceab3de004e990f80d881c6cc00  # v5.5.0
         with:
           directory: ./coverage

filename: .github/workflows/coverage-linux.yml
patch: @@ -84,6 +84,6 @@ jobs:
       - name: Clean tmp
         run: rm -rf coverage/tmp && rm -rf out
       - name: Upload
-        uses: codecov/codecov-action@39a2af19d997be74586469d4062e173ecae614f6  # v5.4.3+
+        uses: codecov/codecov-action@fdcc8476540edceab3de004e990f80d881c6cc00  # v5.5.0
         with:
           directory: ./coverage

filename: .github/workflows/coverage-windows.yml
patch: @@ -71,6 +71,6 @@ jobs:
       - name: Clean tmp
         run: npx rimraf ./coverage/tmp
       - name: Upload
-        uses: codecov/codecov-action@39a2af19d997be74586469d4062e173ecae614f6  # v5.4.3+
+        uses: codecov/codecov-action@fdcc8476540edceab3de004e990f80d881c6cc00  # v5.5.0
         with:
           directory: ./coverage
Repository: ollama/ollama
Pull request: types/model: allow _ as starter character in Name parts


Changed files:
filename: types/model/name.go
patch: @@ -109,19 +109,19 @@ type Name struct {
 //		  { model }
 //		  "@" { digest }
 //	  host:
-//	      pattern: alphanum { alphanum | "-" | "_" | "." | ":" }*
+//	      pattern: { alphanum | "_" } { alphanum | "-" | "_" | "." | ":" }*
 //	      length:  [1, 350]
 //	  namespace:
-//	      pattern: alphanum { alphanum | "-" | "_" }*
+//	      pattern: { alphanum | "_" } { alphanum | "-" | "_" }*
 //	      length:  [1, 80]
 //	  model:
-//	      pattern: alphanum { alphanum | "-" | "_" | "." }*
+//	      pattern: { alphanum | "_" } { alphanum | "-" | "_" | "." }*
 //	      length:  [1, 80]
 //	  tag:
-//	      pattern: alphanum { alphanum | "-" | "_" | "." }*
+//	      pattern: { alphanum | "_" } { alphanum | "-" | "_" | "." }*
 //	      length:  [1, 80]
 //	  digest:
-//	      pattern: alphanum { alphanum | "-" | ":" }*
+//	      pattern: { alphanum | "_" } { alphanum | "-" | ":" }*
 //	      length:  [1, 80]
 //
 // Most users should use [ParseName] instead, unless need to support
@@ -264,7 +264,7 @@ func isValidPart(kind partKind, s string) bool {
 	}
 	for i := range s {
 		if i == 0 {
-			if !isAlphanumeric(s[i]) {
+			if !isAlphanumericOrUnderscore(s[i]) {
 				return false
 			}
 			continue
@@ -280,16 +280,16 @@ func isValidPart(kind partKind, s string) bool {
 				return false
 			}
 		default:
-			if !isAlphanumeric(s[i]) {
+			if !isAlphanumericOrUnderscore(s[i]) {
 				return false
 			}
 		}
 	}
 	return true
 }
 
-func isAlphanumeric(c byte) bool {
-	return c >= 'A' && c <= 'Z' || c >= 'a' && c <= 'z' || c >= '0' && c <= '9'
+func isAlphanumericOrUnderscore(c byte) bool {
+	return c >= 'A' && c <= 'Z' || c >= 'a' && c <= 'z' || c >= '0' && c <= '9' || c == '_'
 }
 
 func cutLast(s, sep string) (before, after string, ok bool) {

filename: types/model/name_test.go
patch: @@ -103,6 +103,8 @@ func TestParseNameParts(t *testing.T) {
 var testCases = map[string]bool{ // name -> valid
 	"": false,
 
+	"_why/_the/_lucky:_stiff": true,
+
 	// minimal
 	"h/n/m:t@d": true,
 
@@ -167,7 +169,6 @@ func TestNameIsValid(t *testing.T) {
 	var numStringTests int
 	for s, want := range testCases {
 		n := ParseNameBare(s)
-		t.Logf("n: %#v", n)
 		got := n.IsValid()
 		if got != want {
 			t.Errorf("parseName(%q).IsValid() = %v; want %v", s, got, want)
Repository: denoland/deno
Pull request: fix(console): prevent multi-line object values in console.table

## Summary

- Objects in `console.table` could break the table layout when their `Deno.inspect` output exceeded the default `breakLength` (72 chars), causing some rows to wrap across multiple lines
- Fix: set `breakLength: Infinity` in the inspect options for table cell values, ensuring single-line rendering

Before:
```
│     1 │ "371fe41e-..." │ { id: "371fe41e-...",
  name: "Deutsche Bahn",
  countryCode: "DE" } │
```

After:
```
│     1 │ "371fe41e-..." │ { id: "371fe41e-...", name: "Deutsche Bahn", countryCode: "DE" } │
```

Fixes #18828

## Test plan

- [x] Added unit test in `console_test.ts` verifying objects with long values stay on single line

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Changed files:
filename: ext/web/01_console.js
patch: @@ -3771,6 +3771,7 @@ class Console {
         ...getConsoleInspectOptions(noColorStdout()),
         depth: 1,
         compact: true,
+        breakLength: Infinity,
       });
     const toTable = (header, body) => this.log(cliTable(header, body));
 

filename: tests/unit/console_test.ts
patch: @@ -1722,6 +1722,35 @@ Deno.test(function consoleTable() {
 `,
     );
   });
+  // Objects with long values should stay on a single line (#18828)
+  mockConsole((console, out) => {
+    console.table([
+      ["b0a6d0c1-7b6c-4fea-9efa-cb2629ce6068", {
+        id: "b0a6d0c1-7b6c-4fea-9efa-cb2629ce6068",
+        name: "Trenitalia",
+        countryCode: "IT",
+      }],
+      ["371fe41e-349c-40b7-be93-10c58fbbb95f", {
+        id: "371fe41e-349c-40b7-be93-10c58fbbb95f",
+        name: "Deutsche Bahn",
+        countryCode: "DE",
+      }],
+    ]);
+    const output = stripAnsiCode(out.toString());
+    // Each row should be a single line (no newlines within cell values)
+    const rows = output.split("\n").filter((line) => line.startsWith("│"));
+    for (const row of rows) {
+      // The row should not contain embedded newlines (the cell value should be flat)
+      assert(!row.includes("\n  "), "Table row should be single-line");
+    }
+    // Verify object values are rendered on one line
+    assert(
+      output.includes(
+        'name: "Deutsche Bahn", countryCode: "DE"',
+      ),
+      "Object should be on single line",
+    );
+  });
   mockConsole((console, out) => {
     console.table([]);
     assertEquals(
Repository: huggingface/transformers
Pull request: Add conditional checks to _check_and_adjust_attn_implementation()

# What does this PR do?

<!--
Congratulations! You've made it this far! You're not quite done yet though.

Once merged, your PR is going to appear in the release notes with the title you set, so make sure it's a great title that fully reflects the extent of your awesome contribution.

Then, please replace this with a description of the change and which issue is fixed (if applicable). Please also include relevant motivation and context. List any dependencies (if any) that are required for this change.

Once you're done, someone will review your PR shortly (see the section "Who can review?" below to tag some potential reviewers). They may suggest changes to make the code even better. If no one reviewed your PR after a week has passed, don't hesitate to post a new comment @-mentioning the same persons---sometimes notifications get lost.
-->

To prevent unnecessary downloads by kernels, avoid installing kernels-community/flash-attn and kernels-community/vllm-flash-attn3 when attn_implementation=flash_attention_2 is specified for NPU.


## test 

### script
```
from transformers import AutoModelForCausalLM, AutoTokenizer

model = AutoModelForCausalLM.from_pretrained(
    "Qwen/Qwen3-0.6B",
    device_map="auto",
    torch_dtype="auto",
    attn_implementation="flash_attention_2",
).eval()
print("Operation successful")
```

### Before
```
`torch_dtype` is deprecated! Use `dtype` instead!
Fetching 0 files: 0it [00:00, ?it/s]
Traceback (most recent call last):
  File "/root/kernels-main/src/kernels/utils.py", line 144, in install_kernel
    return _load_kernel_from_path(repo_path, package_name, variant_locks)
  File "/root/kernels-main/src/kernels/utils.py", line 177, in _load_kernel_from_path
    raise FileNotFoundError(
FileNotFoundError: Kernel at path `/root/.cache/huggingface/hub/models--kernels-community--flash-attn/snapshots/90b3e941627659b28ff001c08b218315e1b7183b` does not have build: torch27-cxx11-cann81-aarch64-linux
```

### After
```
`torch_dtype` is deprecated! Use `dtype` instead!
Operation successful
```


Changed files:
filename: src/transformers/modeling_utils.py
patch: @@ -2499,6 +2499,7 @@ def _check_and_adjust_attn_implementation(
             and self._supports_flash_attn
             and not (is_flash_attn_2_available() or is_flash_attn_3_available())
             and is_kernels_available()
+            and not is_torch_npu_available()
         ):
             if attn_implementation.endswith("2"):
                 applicable_attn_implementation = "kernels-community/flash-attn"
Repository: vercel/next.js
Pull request: make withRspack idempotent

`loadConfig` can get called multiple times in a build or dev session.

in `dev` it gets called multiple times at the end of a session and of course whenever a session restarts
in `build` it can get called multiple times due to build workers

For that reason it needs to be idempotent, so change `withRspack` to detect if it has  already run and short circuit.  Otherwise it will always fail the second time complaining that you passed `--wepack` (because the first run deleted the TURBOPACK env var).

See discussion: https://github.com/vercel/next.js/pull/84394#issuecomment-3364615461


Closes PACK-5621

Changed files:
filename: packages/next-rspack/index.js
patch: @@ -1,11 +1,16 @@
+Error.stackTraceLimit = 100
 module.exports = function withRspack(config) {
-  process.env.NEXT_RSPACK = 'true'
-  process.env.RSPACK_CONFIG_VALIDATE = 'loose-silent'
+  if (process.env.NEXT_RSPACK === 'true') {
+    // we have already been called.  This can happen when using build workers.
+    return config
+  }
   if (process.env.TURBOPACK === 'auto') {
-    // If next has defaulted to turbopack, override it.
     delete process.env.TURBOPACK
+    process.env.RSPACK_CONFIG_VALIDATE = 'loose-silent'
+    process.env.NEXT_RSPACK = 'true'
   } else {
-    console.error(
+    // Either The TURBOPACK flag wasn't set which means --wepack was, or the TURBOPACK flag was set to 1 because --turbopack was passed.
+    console.trace(
       `Cannot call withRspack and pass the ${process.env.TURBOPACK ? '--turbopack' : '--webpack'} flag.`
     )
     console.error('Please configure only one bundler.')