Closed aezur closed 1 year ago
Thank you for noticing this! yes there is a Bug there, I think the problem is that we first publish to npm and then bump the package's version, it will be fixed in the next version. thanks again
I have the same error with 1.0.2 on npm run dev:
ℹ A new version of Nuxt Mongoose (v1.0.2) is available: https://github.com/arashsheyda/nuxt-mongoose/releases/latest
package-lock.json:
"node_modules/nuxt-mongoose": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/nuxt-mongoose/-/nuxt-mongoose-1.0.2.tgz",
"integrity": "sha512-g+O5nqr5NfLQcXEWU68XWypNrlgr7V1v3L0FmNeYELuzK5pePhDCq3tpoDQ3eqUpJr7+InlwqxBKuZ3WK2LkWQ==",
"dev": true,
"dependencies": {
"@nuxt/devtools-kit": "^0.8.4",
"@nuxt/devtools-ui-kit": "^0.8.4",
"@nuxt/kit": "^3.7.3",
"@vueuse/core": "^10.4.1",
"defu": "^6.1.2",
"fs-extra": "^11.1.1",
"mongoose": "^7.5.2",
"ofetch": "^1.3.3",
"pathe": "^1.1.1",
"pluralize": "^8.0.0",
"sirv": "^2.0.3"
},
"funding": {
"url": "https://github.com/sponsors/arashsheyda"
}
},
sorry about that, I did the same mistake again :(
I still see this issue. I have 1.0.5 installed but the error message is still present:
A new version of Nuxt Mongoose (v1.0.5) is available: https://github.com/arashsheyda/nuxt-mongoose/releases/latest
$ npm list | grep "nuxt-mongoose"
├── nuxt-mongoose@1.0.5
@lupus78 thanks for notifying, but this happens when the module is published to npm before that the version is changed, I sometimes forget about it and then this happens.
When building my project I get the message
A new version of Nuxt Mongoose (v0.0.9) is available: https://github.com/arashsheyda/nuxt-mongoose/releases/latest
.I have v0.0.9 installed.