sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Tracking Issue for `io::const_error!`
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(io_const_error)]`

This is a tracking issue for `const_error!`, a macro to create `io::Error`s from a string literal without allocating.

### Public API

```rust
// std::io

macro const_error($kind:expr, $message:expr $(,)?) { ... }
```

### Steps / History

- [x] ACP: https://github.com/rust-lang/libs-team/issues/205
- [ ] Implementation: #...
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

### Unresolved Questions

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: react
Issue: [Compiler Bug]: React Hook placement prevents memoization of dependent variables
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [X] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAHQHYIB4AcIwAuABAGZQZyECWEGxAMtWIQBQCUxwmxxcdLYgBtmJALzEoYBExYcA3Dz4CSAEwCGhdcQlSEAEU3qFmJfwyDcMCIjDTVs8cQDmCQgAVrt+49YiW7Ir0ktIAyhAAtm4AFtQYzgrEAPRJxACyEABuCMSEsWDE0RAQANbEAEYIpAQ5IljE6uVZCKbB5oIYEKoIBRIaWgB0Eeq4rKyd3ZxiAHxcSrztJP6EAJKECBE6xFY2PT6iANoTCAPUqgC6Qby8MG6w9NzB18QDr8cANPPXkFF5cc7IYSiNYbAY-GL-T5PYgAXyusMCrRudxg9FYXwAPABhSL4LAYEjHMBiYBEmHJaZKREYGGYEAwoA

### Repro steps

I noticed an interesting behavior in the compiler. If you place a React hook between two variables that depend on each other, the compiler skips memoizing them. But if you move the hook somewhere else (like above both variables), the memoization works as expected.

| Hook between | Hook above |
| - | - |
|![Screenshot 2024-11-25 at 13 40 07](https://github.com/user-attachments/assets/5e5e691d-94bf-47e5-bed9-72ccced1def8)|![Screenshot 2024-11-25 at 13 40 23](https://github.com/user-attachments/assets/e45cd841-1f46-4ec7-81f3-0c13a31b565a)|


### How often does this bug happen?

Every time

### What version of React are you using?

19.0.0-rc.1

### What version of React Compiler are you using?

19.0.0-beta-0dec889-20241115
Repository: godot
Issue: Cannot look among all items when using Quick Open and Quick Open Script anymore
Labels: discussion,topic:editor,usability,regression

- *Related to https://github.com/godotengine/godot/issues/98726
and https://github.com/godotengine/godot/pull/56772.*

### Tested versions

- Reproducible in: 4.4.dev5
- Not reproducible in: 4.3.stable

### System information

Godot v4.4.dev (9e6098432) - Fedora Linux 41 (KDE Plasma) on X11 - X11 display driver, Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4090 (nvidia; 565.57.01) - 13th Gen Intel(R) Core(TM) i9-13900K (32 threads)

### Issue description

I can't look among all items when using Quick Open and Quick Open Script anymore. This is useful to do in small/medium projects where you want to comb through all of them:

![Image](https://github.com/user-attachments/assets/4d954e4b-6dbf-4f2e-bc23-59c95563dd5a)

As soon as I enter a character, I can see something:

![Image](https://github.com/user-attachments/assets/94999cff-1da4-4253-8843-1717d571754f)

The generic Quick Open dialog is also affected:

![Image](https://github.com/user-attachments/assets/dd08231a-ddc4-4413-8a5e-be6e8934507d)

The workaround is to search for `.` as this will find all files with an extension (including C# in a C#-enabled build), but we should be able to look for files in the list without entering anything.

In comparison, in 4.3.stable, I can see the list of scripts without having to enter anything in the search field:

![Image](https://github.com/user-attachments/assets/bf203d2c-2fe9-45f4-8a93-b78217d4035c)

This issue doesn't occur with Quick Open Scene, where I can see the list of scenes without needing to enter anything in the search field:

![Image](https://github.com/user-attachments/assets/8ae4c923-3689-488a-be85-a19fc136b9ef)

### Steps to reproduce

- Press <kbd>Ctrl + Alt + O</kbd> (Quick Open Script) or <kbd>Alt + Shift + O</kbd> (Quick Open) in the editor.

### Minimal reproduction project (MRP)

https://github.com/godotengine/godot-benchmarks, but any project with several scenes/scripts will do
Repository: TypeScript
Issue: JSDoc property modifiers on computed properties
Labels: Bug,Help Wanted

### 🔎 Search Terms

All declarations of '{property}' must have identical modifiers
JSDoc
Symbol
Computed Property Names
Property Modifiers

### 🕗 Version & Regression Information

This is the behavior in every version I tried (4.X.X - 5.X.X)


### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.7.2&filetype=js#code/MYewdgzgLgBA1gIQIYCcYF4YGUCeBbAIxABsAKAIgNXIEoBuAKAeGKQghgDMQQAGGAN4MYImAHoAVBOGiYEmAAEADihBQApsA0ATGaPkKoOJesEwwAV2LEYAHxjQUASzABzGAF89IiWO8BtRFQAXQxzK2I6cTEYAB4AWniYAEFrGG1NVhQkKCdwDhBOGAByQOQUYOKYPAtoGAALJAA3UycMsFzgJBs8EG0nTid1FAgmWVd1WCoUUhpBb1kUSYsUMBgoeqcIMpDGWS9ZSWlZOUUjEzNHF3cD2V9vCEmYadIm7ot1OaET0Q2tnYqYTexA+e1EXi8zFY7C4PAAjPNDlIFgYVGpNDoUWdjKYBOE0vYrm5PCi-LIAPrk6ZhSzWKJiGIJJIAeTgY1EEymqFmiJ+MCWUBWaz+EAAdJTpmCRLcREcsYYcZcoM5iTKfGTRI8uTNgR8vgtfpsxRLUED3uopSSPEA

### 💻 Code

```js
const kBar = Symbol("bar");

class foo0 {
    /**
     * @protected
     * @type { null | string }
     */
    [kBar] = null; // <-- All declarations of '[kBar]' must have identical modifiers

    get bar() {
        return this[kBar];
    }
    /**
     * @type { string }
     */
    set bar(value) {
        this[kBar] = value;
    }
}
```


### 🙁 Actual behavior

`All declarations of '[kBar]' must have identical modifiers`
but if non-symbol key is used, no error occurs

```js
class foo1 {
    /**
     * @protected
     * @type { null | string }
     */
    __bar = null; // <-- Ok

    get bar() {
        return this.__bar;
    }
    /**
     * @type { string }
     */
    set bar(value) {
        this.__bar = value;
    }
}
```

### 🙂 Expected behavior

Symbol key behave same as string key

### Additional information about the issue

using exact same annotations on every symbol-property assigment allow avoid this error,
but property type becomes `any`
```js
const kBar = Symbol("bar");

class foo0 {
    /**
     * @protected
     * @type { null | string }
     */
    [kBar] = null; // <-- Ok

    get bar() {
        return this[kBar];
    }
    /**
     * @type { string }
     */
    set bar(value) {
        /**
         * @protected
         * @type { null | string }
         */
        this[kBar] = value;
    }
}
```
Repository: vscode
Issue: Git commands do not work if the profile folder name does not contain ASCI characters
Labels: bug,git


Type: <b>Bug</b>

Perform any git command from vs code (pull/push/clone)

result:
> git pull --tags origin master
Could not create directory '/c/Users/\335\344\343\340\360/.ssh' (No such file or directory).
Failed to add the host to the list of known hosts (/c/Users/\335\344\343\340\360/.ssh/known_hosts).
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Commands from console and other clients works fine

VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 5800X 8-Core Processor              (16 x 3800)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|31.91GB (17.29GB free)|
|Process Argv|--disable-extensions --crash-reporter-id c8391010-3648-499c-8f2b-043a2f1aee5c|
|Screen Reader|no|
|VM|50%|
</details>Extensions disabled<details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
9c06g630:31013171
dvdeprecation:31068756
dwnewjupytercf:31046870
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc1:31185841
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530

```

</details>

<!-- generated by issue reporter -->
Repository: TypeScript
Issue: JSDoc implements with imported types
Labels: Bug,Help Wanted

### 🔎 Search Terms

Declaration emit for this file requires using private name '__type' from module '{path}'. An explicit type annotation may unblock declaration emit
implements
import
type
JSDoc

### 🕗 Version & Regression Information

This is the behavior in every version I tried (v5.5.4 - Nightly)


### ⏯ Playground Link

https://www.typescriptlang.org/play/?jsx=0&module=0&ts=5.5.4&filetype=js#code/PTAEAEDMEsBsFMB2BDAtvAXKSB7HA6AKwGcAoYAKgtNAogBcBPAB3gBN5JQBvH7PLMXoAnaIgDmoAL7TQAMTw0KwUuTBQ4SNJlAAjZMKJlKFcNFTMcw+nwU5ZkYTlSgARPmC4CJV7RXkqMwsEdER6Yh47GWVSAGNYZGIIgCEDPhBQAB4AWmzQABF4eINkemgcRFB4VGgbXGFQegALaAiYBFBheABHAFdoLoje4jFJZlEAN1L4UBR0UAByAH0lplYF-FAAQUr4AA9mWGhY2saWGeRERBx6UvLK1GRGUF7EXVgcWIBrUA5i4TuFSqNXo+BooAhXlAAF43AAWABMrgA3KQpEA

### 💻 Code

```js
// @filename: foo.js
/**
 * @typedef { { foo: string } } Foo
 */

// @filename: bar.js
/**@import { Foo } from "./foo.js" */

/**@implements {Foo} */
class Bar { // <-- Declaration emit for this file requires using private name '__type'. An explicit type annotation may unblock declaration emit.
    foo = "42";
}
```


### 🙁 Actual behavior

`Declaration emit for this file requires using private name '__type'. An explicit type annotation may unblock declaration emit`

### 🙂 Expected behavior

no errors.
same code in typescript files works fine.

### Additional information about the issue

if redefine type in the same file, error can be avoided
```js
// @filename: foo.js
/**
 * @typedef { { foo: string } } Foo
 */

// @filename: bar.js
/**
 * @import { Foo } from "./foo.js"
 * @typedef { Foo } $Foo
 */

/**@implements {$Foo} */
class Bar { // <-- Ok
    foo = "42";
}
```
Repository: vscode
Issue: Cannot create file or folder in root directory
Labels: info-needed

![Image](https://github.com/user-attachments/assets/ff7c8bc9-75c6-4201-ab30-d16dcf6ba112)
![Image](https://github.com/user-attachments/assets/977a7dad-267d-4dd1-b985-df3e334e45dc)

Macbook Sequoia 15.1.1,  Visual Studio Code 1.95.3

After opening the project in VS Code, I am unable to create files or folders in the project root directory, but everything works fine in the other folders within the project. I have tried disabling all extensions, but the issue persists. Additionally, the permissions for the project folders are normal.
Repository: opencv
Issue: videoio: capture by index/name check is wrong on failure with API preference set
Labels: bug,category: videoio

### System Information

OpenCV version: 4.10.0 (checked: still the same code in 4.x & 5.x branch)

### Detailed description

#22700 introduced a check to print the `backend is generally available but can't be used to capture by index/name` message.
however, this message is also printed even if the backend does support the capture mode but it couldn't open the capture device for another reason.

i think the proper thing to do is to check the capabilities of the backend before issuing the message, i.e. check for `MODE_CAPTURE_BY_INDEX` and `MODE_CAPTURE_BY_FILENAME` (what about `MODE_WRITER`?).

at a first glance there doesn't seem to be an API to get the mode right now? so this might need an extension to `videoio_registry.cpp` to add `getBackendMode` or similar?

### Steps to reproduce

1. build with aravis support (`HAVE_ARAVIS=ON`)
2. try to create a new video capture for this: `cv::VideoCapture cap(0, cv::CAP_ARAVIS);` (or `cv::VideoCapture cap("foo", cv::CAP_ARAVIS);`)
3. run this code (w/o an USB3 VISION / GigE VISION camera attached)

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: vscode
Issue: Git - Git blame editor decoration color
Labels: bug,git,ux

With `git.blame.editorDecoration.enabled`. I was expecting it to pick up my theme's comment color as the default color since that's the closest thing to what it is:

![Image](https://github.com/user-attachments/assets/6575b653-37f1-4437-afcb-0cd842ad4308)

Personally I want it to be very subtle just like comments.
Repository: vscode
Issue: Git blame editor decoration leverage horizontal space?
Labels: feature-request,scm

What it looks like currently:

![Image](https://github.com/user-attachments/assets/31b9fda5-9317-4d1e-b247-efa0a2387dba)

If I zoom out though it reveals a lot of unused space:

![Image](https://github.com/user-attachments/assets/7d9d6116-1a19-42b0-898b-09713b6e33d7)

Instead of cluttering things, perhaps it makes sense to allow users to position them at the ruler(s) which are often where a user wraps their code.
Repository: angular
Issue: linkedSignal / resource: small APIs inconsistency
Labels: area: core,core: reactivity,cross-cutting: signals

### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

Hey! 

I've being playing with `linkedSignal` and `resource` in the last few days. Just a small remark on the new APIs: 

```ts
  linked = linkedSignal({
    source: () => this.params(),
    computation: (one, two) => {...},
  });

  resource = resource({
    request: () => this.params(),
    loader: ({ request, previous }) => {...},
  });
```

Maybe I'm missing something obvious, but ideally I'd like to have computation / loader treated the same way: 

```ts
  linked = linkedSignal({
    source: () => this.params(),
    computation: ({ source, previous }) => {...},
  });

  resource = resource({
    request: () => this.params(),
    loader: ({ request, previous }) => {...},
  });
```

Not a huge deal, but still... I think it would be nice to align the APIs (assuming I'm not missing something else). 

### Proposed solution

```ts
  linked = linkedSignal({
    source: () => this.params(),
    computation: ({ source, previous }) => {...},
  });

  resource = resource({
    request: () => this.params(),
    loader: ({ request, previous }) => {...},
  });
```
Repository: three.js
Issue: GLTFLoader: Assets with url-encoded UTF8 characters in filenames don't load correctly
Labels: Loaders

### Description

While tackling various internationalization issues with glTF assets I made a few new test assets:
- https://github.com/KhronosGroup/glTF-Sample-Assets/pull/157 

In general, three.js fares second-best of the viewers I tested, but one asset doesn't load at all, thus this report.

### Reproduction steps

See live example or code.

This URL works: https://raw.githubusercontent.com/prefrontalcortex/glTF-Sample-Assets/sample/relativeUris/Models/UriTest/glTF-UriTest-01-RelativeTexture-NoUTF8/RelativeResourcePaths.gltf

This URL does not work: https://raw.githubusercontent.com/prefrontalcortex/glTF-Sample-Assets/sample/relativeUris/Models/UriTest/glTF-UriTest-02-RelativeTexture-UTF8/RelativeResourcePaths.gltf

Here's ZIP files of the assets:

[glTF-UriTest-01-RelativeTexture-NoUTF8.zip](https://github.com/user-attachments/files/17904155/glTF-UriTest-01-RelativeTexture-NoUTF8.zip)
[glTF-UriTest-02-RelativeTexture-UTF8.zip](https://github.com/user-attachments/files/17904156/glTF-UriTest-02-RelativeTexture-UTF8.zip)

Both assets pass the glTF Validator and load in e.g. UnityGLTF or glTFast. Other viewers also have issues with URL-encoded UTF8 characters in path names.

### Code

```js
const loader = new GLTFLoader();
    loader.load(
    	// Working URL (non-UTF8):
      // 'https://raw.githubusercontent.com/prefrontalcortex/glTF-Sample-Assets/sample/relativeUris/Models/UriTest/glTF-UriTest-01-RelativeTexture-NoUTF8/RelativeResourcePaths.gltf',
      // Broken URL (UTF8):
      'https://raw.githubusercontent.com/prefrontalcortex/glTF-Sample-Assets/sample/relativeUris/Models/UriTest/glTF-UriTest-02-RelativeTexture-UTF8/RelativeResourcePaths.gltf',
      // called when the resource is loaded
      function ( gltf ) {
        scene.add( gltf.scene );
      }
    );
```


### Live example

https://jsfiddle.net/st52uj40/10/

### Screenshots

<img width="719" alt="image" src="https://github.com/user-attachments/assets/2a0a7421-0602-4912-846f-a5fbfbd9f3b5">


### Version

latest

### Device

_No response_

### Browser

_No response_

### OS

_No response_
Repository: vscode
Issue: Editor GPU: Bracket pair colorization doesn't update when theme is changed
Labels: bug,editor-gpu

Repro:

1. editor gpu rendering on
2. Change `workbench.colorCustomizations.editorBracketHighlight.foreground*` settings
3. Save, 🐛 existing editors don't update
Repository: vscode
Issue: Editor GPU: Support non-regular inline decorations
Labels: plan-item,editor-gpu

See https://github.com/microsoft/vscode/pull/234579
Repository: kubernetes
Issue: DRA: seamless kubelet plugin upgrade
Labels: sig/node,kind/feature,needs-triage,wg/device-management

### What would you like to be added?

When updating the DaemonSet of a DRA driver, ideally we want that to be seamless:
- minimal period of time where the kubelet can't call NodePrepareResources
- no deletion + recreation or updates of ResourceSlices

A DaemonSet supports [rolling updates](https://pkg.go.dev/k8s.io/api/apps/v1#RollingUpdateDaemonSet) such that a new pod is already running on a node in parallel to the old one. It's the default!

We need to ensure that:
- the kubelet can reliably detect stale sockets (covered by https://github.com/kubernetes/kubernetes/issues/128696)
- if two pods register in parallel, the kubelet picks the newer one, regardless of the order in which they register (the kubelet might get restarted and then needs to handle registration in arbitrary order)
- there's clear documentation on how to configure a DRA driver daemonset (which socket paths should it use - the same for both pods or per-pod?) and that the example driver follows those best practices

/sig node
/wg device-management
/cc @SergeyKanzhelev 

### Why is this needed?

Less downtime, faster updates.
Repository: kubernetes
Issue: DRA: version skew testing
Labels: sig/node,kind/feature,needs-triage,wg/device-management

### What would you like to be added?

Upgrading a 1.31 alpha cluster to 1.32 with only the beta API enabled is supported. We should have automated tests for version skew and upgrade scenarios:
- creating a v1alpha3 ResourceClaim, upgrading to 1.32 beta, getting it allocated
- creating a DaemonSet with admin access enabled, upgrading to 1.32 with admin access disabled =>
  - scheduled, not-running pods should start with admin access
  - not-scheduled pods should not get scheduled (error in scheduler: "feature not enabled"), without adverse affects on the DaemonSet controller (like re-creating pods)
- kubelet from v1.31 with control plane from v1.32 with v1alpha3 API enabled => can start pods with claims

Later, downgrades also need to be tested. At the moment, downgrades from 1.32 to 1.31 are not supported (storage version is v1beta1, not supported by 1.31).


### Why is this needed?

Test coverage. Good for production readiness when considering GA.
Repository: rust
Issue: The default values for TargetOption violate the target consistency check
Labels: T-compiler,A-target-specs,C-bug,A-targets

`TargetOption` defaults to `relocation_model: Pic` and `dynamic_linking: false` and `position_independent_executables: false`. However, our consistency check that this is an invalid combination of options.

So it seems we should either fix our defaults, or the consistency check is a bit overzealous?

This check was added in https://github.com/rust-lang/rust/pull/100537, Cc @petrochenkov @oli-obk
Repository: vscode
Issue: Not displaying completion items with empty string text labels
Labels: suggest,under-discussion

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.95.3
- OS Version: Darwin arm64 23.4.0

Steps to Reproduce:

1.  [TypeScript Playground](https://www.typescriptlang.org/play/?#code/MYGwhgzhAEBCCuBzaBvAUNTmBOBTR842ACtgPYAO0AvNAOQDuZ2A1hHRlvd7YwBYBLAC64IFMMFwcu3CnRr1xAEyW4l0rnXm9cAWwpCAnvOicsaAL5o0oSDABKuCiGi4AHiIB2SmAmToZYDJPCCFseGAhZgAKAEpUMxlMCHgKXGw4xKSAemzoTzIGaDDDYrJoCUkoYr5cV30jaFDsAU9kCnI07EaGYT5oACNsCRZcIQgsmSFBCABtLQBdLKsrayA)
```ts
class Bug {
     ' ' = 'whitespace'
     ' p' = 'padded'
     '' = 'empty'  
}

class Repl extends Bug {
     constructor() {
          super()
          // now try to access the empty string property with brackets
          this[''] // receives 3 entries from Typescript, displays only 2

     }

}
```

![Image](https://github.com/user-attachments/assets/348110a4-ed8a-4166-91df-70b9f46c62fd)

Entries from  `extensions/typescript-language-features/src/languageFeatures/completions.ts`

```json
[
    {
        "name": "",
        "kind": "property",
        "kindModifiers": "",
        "sortText": "11",
    },
    {
        "name": " ",
        "kind": "property",
        "kindModifiers": "",
        "sortText": "11",
    },
    {
        "name": " p",
        "kind": "property",
        "kindModifiers": "",
        "sortText": "11",
    }
]
```
Repository: storybook
Issue: [Bug]: Nuxt init broken
Labels: bug,cli,vue3,nuxt,sev:S2

### Describe the bug

When I create a new Nuxt project and try to initialize Storybook, it says that the initialization is successful but nothing is installed. I would expect that it would either install the Nuxt framework or the `vue3-vite` framework or to fail with an error.


### Reproduction link

N/A

### Reproduction steps

```sh
npx nuxi@latest init test-nuxt
cd test-nuxt
npx storybook@next init
```

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 15.1.1
    CPU: (10) arm64 Apple M1 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.17.0 - /usr/local/bin/node
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 9.13.2 - ~/Library/pnpm/pnpm <----- active
  Browsers:
    Chrome: 131.0.6778.86
    Safari: 18.1.1
```

### Additional context

_No response_