helloadhavan/github_issues huggingface dataset:
Repository: nodejs/node
Pull request: lib: fix typo in util.js comment

'explictly' -> 'explicitly' in getCallSites function comment

<!--
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: lib/util.js
patch: @@ -453,7 +453,7 @@ function getCallSites(frameCount = 10, options) {
 
   // Using kDefaultMaxCallStackSizeToCapture as reference
   validateNumber(frameCount, 'frameCount', 1, 200);
-  // If options.sourceMaps is true or if sourceMaps are enabled but the option.sourceMaps is not set explictly to false
+  // If options.sourceMaps is true or if sourceMaps are enabled but the option.sourceMaps is not set explicitly to false
   if (options.sourceMap === true || (getOptionValue('--enable-source-maps') && options.sourceMap !== false)) {
     return mapCallSite(binding.getCallSites(frameCount));
   }
Repository: vuejs/vue
Pull request: fix(types): update the type definition of $el property

to be able to define `$el` as `SVGElement`

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->

<!-- PULL REQUEST TEMPLATE -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

**What kind of change does this PR introduce?** (check at least one)

- [x] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:

**Does this PR introduce a breaking change?** (check one)

- [x] Yes
- [ ] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [x] It's submitted to the `dev` branch for v2.x (or to a previous version branch), _not_ the `master` branch
- [x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
- [x] New/updated tests are included

**Other information:**


Changed files:
filename: types/test/vue-test.ts
patch: @@ -19,6 +19,7 @@ class Test extends Vue {
   }
 
   // test property reification
+  $el!: HTMLElement | SVGElement;
   $refs!: {
     vue: Vue,
     element: HTMLInputElement,

filename: types/vue.d.ts
patch: @@ -21,7 +21,7 @@ export interface CreateElement {
 }
 
 export interface Vue {
-  readonly $el: HTMLElement;
+  readonly $el: Element;
   readonly $options: ComponentOptions<Vue>;
   readonly $parent: Vue;
   readonly $root: Vue;
Repository: ggml-org/llama.cpp
Pull request: vulkan: fix flash attention dot product precision

The Q*K^T dot product was done in float16, but it should have been using ACC_TYPE. This fixes the GLM4 incoherence.

Fixes #20555

Changed files:
filename: ggml/src/ggml-vulkan/vulkan-shaders/flash_attn.comp
patch: @@ -245,7 +245,7 @@ void main() {
 #endif
                     }
                     [[unroll]] for (uint32_t r = 0; r < rows_per_thread; ++r) {
-                        Sf[r][c] += ACC_TYPE(dot(Q_cache[r], K_Tf));
+                        Sf[r][c] += dot(ACC_TYPEV4(Q_cache[r]), ACC_TYPEV4(K_Tf));
                     }
                 }
             }
@@ -270,7 +270,7 @@ void main() {
 #endif
                     }
                     [[unroll]] for (uint32_t r = 0; r < rows_per_thread; ++r) {
-                        Sf[r][c] += ACC_TYPE(dot(Qf[tile_row(r) * qf_stride + d * D_split + d_tid], K_Tf));
+                        Sf[r][c] += dot(ACC_TYPEV4(Qf[tile_row(r) * qf_stride + d * D_split + d_tid]), ACC_TYPEV4(K_Tf));
                     }
                 }
             }
Repository: vuejs/vue
Pull request: fix(types): allow using functions on the PropTypes (#9692)

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->

<!-- PULL REQUEST TEMPLATE -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

**What kind of change does this PR introduce?** (check at least one)

- [x] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [x] It's submitted to the `dev` branch for v2.x (or to a previous version branch), _not_ the `master` branch
- [x] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix #xxx[,#xxx]`, where "xxx" is the issue number)
- [x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
- [x] New/updated tests are included

If adding a **new feature**, the PR's description includes:
- [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

**Other information:**


Changed files:
filename: types/options.d.ts
patch: @@ -144,7 +144,7 @@ export interface RenderContext<Props=DefaultProps> {
   injections: any
 }
 
-export type Prop<T> = { (): T } | { new(...args: any[]): T & object }
+export type Prop<T> = { (): T } | { new(...args: any[]): T & object } | { new(...args: string[]): Function }
 
 export type PropType<T> = Prop<T> | Prop<T>[];
 

filename: types/test/options-test.ts
patch: @@ -68,12 +68,14 @@ interface ICat {
   foo: any,
   bar: object
 }
+type ConfirmCallback = (confirm: boolean) => void;
 
 Vue.component('union-prop', {
   props: {
     cat: Object as PropType<ICat>,
     complexUnion: { type: [User, Number] as PropType<User | number> },
     kittyUser: Object as PropType<ICat & IUser>,
+    callback: Function as PropType<ConfirmCallback>,
     mixed: [RegExp, Array],
     object: [Cat, User],
     primitive: [String, Number],
@@ -84,6 +86,7 @@ Vue.component('union-prop', {
     this.cat;
     this.complexUnion;
     this.kittyUser;
+    this.callback(true);
     this.mixed;
     this.object;
     this.primitive;
@@ -281,6 +284,18 @@ Vue.component('component', {
   delimiters: ["${", "}"]
 });
 
+
+Vue.component('custom-prop-type-function', {
+  props: {
+    callback: Function as PropType<(confirm: boolean) => void>,
+  },
+  methods: {
+    confirm(){
+      this.callback(true);
+    }
+  }
+});
+
 Vue.component('provide-inject', {
   provide: {
     foo: 1
Repository: nodejs/node
Pull request: tools: update nixpkgs-unstable to be5afa0fcb31f0a96bf9ecba05a516c66fc

This is an automated update of nixpkgs-unstable to be5afa0fcb31f0a96bf9ecba05a516c66fc.

Changed files:
filename: tools/nix/pkgs.nix
patch: @@ -1,10 +1,10 @@
 arg:
 let
   repo = "https://github.com/NixOS/nixpkgs";
-  rev = "3146c6aa9995e7351a398e17470e15305e6e18ff";
+  rev = "be5afa0fcb31f0a96bf9ecba05a516c66fcd8114";
   nixpkgs = import (builtins.fetchTarball {
     url = "${repo}/archive/${rev}.tar.gz";
-    sha256 = "165ql727hrcjz3zwsah18zclf5znfry7dc042qxc2zixsqqzah7a";
+    sha256 = "0jm942f32ih264hmna7rhjn8964sid0sn53jwrpc73s2vyvqs7kc";
   }) arg;
 in
 nixpkgs
Repository: ollama/ollama
Pull request: CONTRIBUTING: fix code block formatting

There were only 3 spaces instead of 4, so the example was being considered to include html elements

Changed files:
filename: CONTRIBUTING.md
patch: @@ -51,7 +51,7 @@ see if the change were accepted.
 
 The title should look like:
 
-   <package>: <short description>
+    <package>: <short description>
 
 The package is the most affected Go package. If the change does not affect Go
 code, then use the directory name instead. Changes to a single well-known
Repository: nodejs/node
Pull request: src: use C++ nullptr in sqlite

Refs: https://github.com/nodejs/node/pull/61407

<!--
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: src/node_sqlite.cc
patch: @@ -1235,7 +1235,7 @@ void DatabaseSync::Prepare(const FunctionCallbackInfo<Value>& args) {
 
   Utf8Value sql(env->isolate(), args[0].As<String>());
   sqlite3_stmt* s = nullptr;
-  int r = sqlite3_prepare_v2(db->connection_, *sql, -1, &s, 0);
+  int r = sqlite3_prepare_v2(db->connection_, *sql, -1, &s, nullptr);
 
   CHECK_ERROR_OR_THROW(env->isolate(), db, r, SQLITE_OK, void());
   BaseObjectPtr<StatementSync> stmt =
@@ -3043,7 +3043,7 @@ BaseObjectPtr<StatementSync> SQLTagStore::PrepareStatement(
   if (stmt == nullptr) {
     sqlite3_stmt* s = nullptr;
     int r = sqlite3_prepare_v2(
-        session->database_->connection_, sql.data(), sql.size(), &s, 0);
+        session->database_->connection_, sql.data(), sql.size(), &s, nullptr);
 
     if (r != SQLITE_OK) {
       THROW_ERR_SQLITE_ERROR(isolate, session->database_.get());
Repository: ollama/ollama
Pull request: digest files in parallel

this significantly improves performance of this function specifically when digesting a directory of many files. this reduces digesting by 90% (20s -> 2s) creating [mistralai/Mistral-Small-3.1-24B-Instruct-2503](https://huggingface.co/mistralai/Mistral-Small-3.1-24B-Instruct-2503)

Changed files:
filename: parser/parser.go
patch: @@ -11,10 +11,13 @@ import (
 	"os"
 	"os/user"
 	"path/filepath"
+	"runtime"
 	"slices"
 	"strconv"
 	"strings"
+	"sync"
 
+	"golang.org/x/sync/errgroup"
 	"golang.org/x/text/encoding/unicode"
 	"golang.org/x/text/transform"
 
@@ -144,12 +147,25 @@ func fileDigestMap(path string) (map[string]string, error) {
 		files = []string{path}
 	}
 
+	var mu sync.Mutex
+	var g errgroup.Group
+	g.SetLimit(max(runtime.GOMAXPROCS(0)-1, 1))
 	for _, f := range files {
-		digest, err := digestForFile(f)
-		if err != nil {
-			return nil, err
-		}
-		fl[f] = digest
+		g.Go(func() error {
+			digest, err := digestForFile(f)
+			if err != nil {
+				return err
+			}
+
+			mu.Lock()
+			defer mu.Unlock()
+			fl[f] = digest
+			return nil
+		})
+	}
+
+	if err := g.Wait(); err != nil {
+		return nil, err
 	}
 
 	return fl, nil
Repository: ollama/ollama
Pull request: Create a new file descriptor for each goroutine during GGML model loading to improve loading from network filesystems.

This fixes #9691 

Ollama currently reuses the same file descriptor across all goroutines reading the model. GCS Fuse (and often other network-based filesystems) only keeps one open download stream per FD, as you cannot seek within a stream. This means every read at a non-sequential offset has to close the existing download and start a new one at the desired offset, which is slow. This happens frequently as each goroutine is reading from a different offset from the same FD. The error in #9691 is because the model cannot be loaded within the timeout.

This fixes the issue by creating a new FD per goroutine, which each goroutine reads sequentally from.

On Cloud Run with the Cloud Storage volume (powered by GCS Fuse), this fixes the issue where model loading just times out. `gemma3:4b` loads in 12s and `gemma3:27b` loads in 32s (measured by model loading time with `OLLAMA_DEBUG=1`. 

I also tested on Google Compute Engine on a `n2-standard-8` (8 vCPUs, 32 GB Memory) with the model stored on both HDD (Standard PD) and local SSD to make sure there's no regressions there (it is expected that we get the same performance between the two branches):

```
% git clone https://github.com/danhipke/ollama.git
% cd ollama
% git checkout newfd
% go build

# test script (new fd per goroutine)
% OLLAMA_MODELS=/mnt/disks/pd OLLAMA_DEBUG=1 ./ollama serve
% OLLAMA_HOST=http://localhost:11434 ~/ollama/ollama run gemma3  # 32s
% OLLAMA_HOST=http://localhost:11434 ~/ollama/ollama run gemma3:27b  # 2min55
% OLLAMA_MODELS=/mnt/disks/localssd OLLAMA_DEBUG=1 ./ollama serve
% OLLAMA_HOST=http://localhost:11434 ~/ollama/ollama run gemma3 # 5s
% OLLAMA_HOST=http://localhost:11434 ~/ollama/ollama run gemma3:27b  # 17s

% git checkout main
% go build
# repeat test above

% OLLAMA_MODELS=/mnt/disks/pd OLLAMA_DEBUG=1 ./ollama serve 
% OLLAMA_HOST=http://localhost:11434 ~/ollama/ollama run gemma3  # 32s
% OLLAMA_HOST=http://localhost:11434 ~/ollama/ollama run gemma3:27b  # 2min55
% OLLAMA_MODELS=/mnt/disks/localssd OLLAMA_DEBUG=1 ./ollama serve
% OLLAMA_HOST=http://localhost:11434 ~/ollama/ollama run gemma3 # 5s 
% OLLAMA_HOST=http://localhost:11434 ~/ollama/ollama run gemma3:27b # 17s
```

Let me know if there's any other testing needed.

Changed files:
filename: ml/backend/ggml/ggml.go
patch: @@ -319,7 +319,14 @@ func New(ctx context.Context, r *os.File, params ml.BackendParams) (ml.Backend,
 				tts[i] = tt
 			}
 
-			sr := io.NewSectionReader(r, int64(meta.Tensors().Offset+t.Offset), int64(t.Size()))
+			// Create a new FD for each goroutine so that each FD is read sequentially, rather than
+			// seeking around within an FD shared between all goroutines.
+			file, err := os.Open(r.Name())
+			if err != nil {
+				return err
+			}
+			defer file.Close()
+			sr := io.NewSectionReader(file, int64(meta.Tensors().Offset+t.Offset), int64(t.Size()))
 			bts := make([]byte, 128*format.KibiByte)
 
 			var s uint64
Repository: vuejs/vue
Pull request: fix(codegen): inline function expression can be named inside a `v-on`…

… expression (fix #9707)

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->

<!-- PULL REQUEST TEMPLATE -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

**What kind of change does this PR introduce?** (check at least one)

- [x] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [x] It's submitted to the `dev` branch for v2.x (or to a previous version branch), _not_ the `master` branch
- [x] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix #xxx[,#xxx]`, where "xxx" is the issue number)
- [x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
- [x] New/updated tests are included

If adding a **new feature**, the PR's description includes:
- [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

**Other information:**


Changed files:
filename: src/compiler/codegen/events.js
patch: @@ -1,6 +1,6 @@
 /* @flow */
 
-const fnExpRE = /^([\w$_]+|\([^)]*?\))\s*=>|^function\s*\(/
+const fnExpRE = /^([\w$_]+|\([^)]*?\))\s*=>|^function\s*(?:[\w$]+)?\s*\(/
 const fnInvokeRE = /\([^)]*?\);*$/
 const simplePathRE = /^[A-Za-z_$][\w$]*(?:\.[A-Za-z_$][\w$]*|\['[^']*?']|\["[^"]*?"]|\[\d+]|\[[A-Za-z_$][\w$]*])*$/
 

filename: test/unit/modules/compiler/codegen.spec.js
patch: @@ -500,6 +500,11 @@ describe('codegen', () => {
       '<input @input="function () { current++ }">',
       `with(this){return _c('input',{on:{"input":function () { current++ }}})}`
     )
+    // normal named function
+    assertCodegen(
+      '<input @input="function fn () { current++ }">',
+      `with(this){return _c('input',{on:{"input":function fn () { current++ }}})}`
+    )
     // arrow with no args
     assertCodegen(
       '<input @input="()=>current++">',
Repository: ggml-org/llama.cpp
Pull request: tests: Fix invalid iterator::end() dereference in common_regex

When compiling with VS2026 18.4 I noticed `test-regex-partial` crashes immediately with debug build. 

<img width="478" height="355" alt="image" src="https://github.com/user-attachments/assets/e5d3b7b3-95f4-491f-a28a-a105678eb72f" />

I tracked this down to an iterator::end() dereference in the following test case which was [occurring here.](https://github.com/ggml-org/llama.cpp/blob/de190154c85d20e24dbeae8c8af1849402ae5098/common/regex-partial.cpp#L105)

```cpp
    assert_equals<std::string>(
        "^(a*)",
        regex_to_reversed_partial_regex("a*"));
```

This fix adds bounds checking to prevent such dereferencing.

Changed files:
filename: common/regex-partial.cpp
patch: @@ -102,7 +102,7 @@ std::string regex_to_reversed_partial_regex(const std::string & pattern) {
                 auto is_star = *it == '*';
                 ++it;
                 if (is_star) {
-                    if (*it == '?') {
+                    if (it != end && *it == '?') {
                         ++it;
                     }
                 }
Repository: nodejs/node
Pull request: sqlite: add some tests

Add some exceptions tests to `sqlite` suite

Changed files:
filename: test/parallel/test-sqlite-aggregate-function.mjs
patch: @@ -68,6 +68,19 @@ describe('DatabaseSync.prototype.aggregate()', () => {
         message: /The "options\.directOnly" argument must be a boolean/,
       });
     });
+
+    test('throws if options.inverse is not a function', (t) => {
+      t.assert.throws(() => {
+        db.aggregate('sum', {
+          start: 0,
+          step: (acc, value) => acc + value,
+          inverse: 10
+        });
+      }, {
+        code: 'ERR_INVALID_ARG_TYPE',
+        message: /The "options\.inverse" argument must be a function/,
+      });
+    });
   });
 });
 

filename: test/parallel/test-sqlite-template-tag.js
patch: @@ -15,6 +15,17 @@ beforeEach(() => {
   sql.clear();
 });
 
+test('throws error if database is not open', () => {
+  const db = new DatabaseSync(':memory:', { open: false });
+
+  assert.throws(() => {
+    db.createTagStore(10);
+  }, {
+    code: 'ERR_INVALID_STATE',
+    message: 'database is not open'
+  });
+});
+
 test('sql.run inserts data', () => {
   assert.strictEqual(sql.run`INSERT INTO foo (text) VALUES (${'bob'})`.changes, 1);
   assert.strictEqual(sql.run`INSERT INTO foo (text) VALUES (${'mac'})`.changes, 1);
Repository: vuejs/vue
Pull request: fix #9727

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->

<!-- PULL REQUEST TEMPLATE -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

**What kind of change does this PR introduce?** (check at least one)

- [x] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [x] It's submitted to the `dev` branch for v2.x (or to a previous version branch), _not_ the `master` branch
- [x] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix #xxx[,#xxx]`, where "xxx" is the issue number)
- [x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
- [ ] New/updated tests are included

If adding a **new feature**, the PR's description includes:

- [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

**Other information:**

This PR fix #9727.

Changed files:
filename: flow/vnode.js
patch: @@ -42,7 +42,7 @@ declare interface VNodeData {
   staticClass?: string;
   class?: any;
   staticStyle?: { [key: string]: any };
-  style?: Array<Object> | Object;
+  style?: string | Array<Object> | Object;
   normalizedStyle?: Object;
   props?: { [key: string]: any };
   attrs?: { [key: string]: string };

filename: types/test/vue-test.ts
patch: @@ -213,3 +213,28 @@ class Decorated extends Vue {
 
 const obj = Vue.observable({ a: 1 })
 obj.a++
+
+// VNodeData style tests.
+const ComponentWithStyleInVNodeData = Vue.extend({
+  render (h) {
+    const elementWithStyleAsString = h('div', {
+      style: 'background-color: red;'
+    });
+
+    const elementWithStyleAsObject = h('div', {
+      style: { backgroundColor: 'green' }
+    });
+
+    const elementWithStyleAsArrayOfObjects = h('div', {
+      style: [
+        { backgroundColor: 'blue' }
+      ]
+    });
+
+    return h('div', undefined, [
+      elementWithStyleAsString,
+      elementWithStyleAsObject,
+      elementWithStyleAsArrayOfObjects
+    ]);
+  }
+});

filename: types/vnode.d.ts
patch: @@ -48,7 +48,7 @@ export interface VNodeData {
   staticClass?: string;
   class?: any;
   staticStyle?: { [key: string]: any };
-  style?: object[] | object;
+  style?: string | object[] | object;
   props?: { [key: string]: any };
   attrs?: { [key: string]: any };
   domProps?: { [key: string]: any };