Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Type errors in v2.4.0

See original GitHub issue

Describe the bug

When upgrading to v2.4.0 I get type errors in my stores for the following config:

export const store = defineStore('myStore', {
  // state, actions, etc.
  persist: {
    paths: [
      'someList',
    ],
    afterRestore: ({ store }) => {
      // do smth... 
    }
  }
})

No problems with v2.3.0…

Screenshot 2022-11-17 at 12 13 33

Reproduction

see code snippet above…

System Info

System:
    OS: macOS 13.0.1
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
    Memory: 41.49 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.11.0 - ~/.nvm/versions/node/v16.11.0/bin/node
    Yarn: 1.22.11 - ~/.nvm/versions/node/v16.11.0/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v16.11.0/bin/npm
  Browsers:
    Brave Browser: 106.1.44.101
    Chrome: 107.0.5304.110
    Firefox: 106.0.1
    Safari: 16.1

Used Package Manager

yarn

Validations

Follow our Code of Conduct
Read the Contributing Guide.
Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
The provided reproduction is a minimal reproducible of the bug.

Issue Analytics

State:
Created 10 months ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

prazdevscommented, Nov 17, 2022

the .nuxt is where most types are automatically generated by nuxt, so it can come from this.

I have in the plans to rework lots of stuff to completely externalize nuxt support and make a proper nuxt module when i have some time 😃

0reactions

prazdevscommented, Nov 26, 2022

v3 is now release with available nuxt module as well! docs are also deployed 🚀 closing this for now, if still having issues, feel free to reopen

Top Results From Across the Web

Error handling - Apollo GraphQL Docs

Apollo Server's variety of error codes enables requesting clients to respond differently to different error types. You can also create your own custom...

v2.4.0 error "bash: seqtk-trinity: command not found" #240

2 / dir. I attempted a completely new run of Trinity and still get the same fail/error state, as shown below in Error...

SigmaLogic AOI v2.4.0 - Yaskawa

Internally, this AOI monitors a 'Heartbeat' input data point from the attached SigmaLogic axis. This heartbeat signal is internally.

Mule Errors | MuleSoft Documentation

Mule errors are grouped into error types that follow a hierarchical order and use a naming convention that helps you identify the source...

TypeScript error TS1005: ';' expected (II) - Stack Overflow

I was using npx tsc <filename> to compile. Weird that npx would use an outdated version? – colefner. Jul 4, 2019 at 5:49....