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.
Package version for @nuxt/types should match nuxt's version
See original GitHub issueIs your feature request related to a problem? Please describe.
For people running an older version of Nuxt, it would be helpful if they could easily tell which version of @nuxt/types most accurately reflected the types in use in their project.
Describe the solution you’d like
Move @nuxt/types to version 2.10.2, and then track nuxt releases.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Setup - Nuxt TypeScript
Types versioning match Nuxt versioning since 2.13.0. Configuration. All you need to do is add @nuxt/typescript-build to your buildModules ...
Read more >Releases - Nuxt TypeScript
Information Note. Warning is now displayed if Nuxt.js version installed is superior or equal to 2.15, which includes built-in support for TypeScript runtime ......
Read more >The build Property - Nuxt
As of Nuxt@2.14 Nuxt automatically detects the current version of core-js in your project, also you can specify which version you want to...
Read more >Configuration - Nuxt
Configuration. By default, Nuxt is configured to cover most use cases. This default configuration can be overwritten with the nuxt.config.js file.
Read more >Release Notes - Nuxt
Discover all the release notes for the Nuxt framework. ... Modules When matching a webpack loader by name or query, should use includes...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@kevinmarrec why can’t the type package match the major and minor version numbers but have a different patch version? Theoretically semantic versioning defines that there shouldn’t be API changes (and hence typing changes) between patch versions.
👍