-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Deprecation Warning on Nuxt.js build due to package.json export #140
Comments
I have the same problem Node v20.1
I tried removing the line specified in the above link and the error disappeared. I'm executing |
I've seen this issue in another project after recent update when import path ends with Maybe there is import somewhere in code that ends with |
Since I couldn't determine the source of the problem, I used the stupidest way to test (deleting files one by one, you need to delete node_modules at the same time and repackage) When I encountered the .npmrc file, I removed the I'm not sure if there's any connection, but it does solve my problem for now |
I also have this in my project Running |
After my investigation, nuxt starter will write a .npmrc file before September 2023 that includes shamefull-hoist=true. This will cause an issue when running pnpm build. However, this file has been removed as of September 2023. Therefore, if the project was created before, it may still have this file. No longer see this warning after manually removing the file. Reference @hmingv Thank you for your helpful response, it saved me from being stuck here like you. |
@hmingv I removed the shamefully-hoist=true line and the problem still exists; |
Are you encountering guys right after you push ur updates in production, the nuxt application will be delayed for a bit of seconds in every page that I navigate? when I already went there on every page, it will become normal navigation again, there's no delay. Is there any connections about this warning or issue of @iconify/vue/ ? btw I deployed my nuxt app using npm run build for ssr in vercel. TIA |
@kleinpetr can we downgrade the nuxt app? |
@Kram-V yes, when I downgrade to |
@kleinpetr ok tnx |
@Kram-V oh sorry, it seems that I am getting these warning also with locked |
Try running |
btw @kleinpetr how can you downgrade ur nuxt app with specific version? |
@kleinpetr I removed the node_modules and package-lock.json and change the version of my nuxt app into ^3.9.3 but when I npm run dev the pop up in the terminal still Nuxt 3.11.2 why is that? |
Remove |
@cyberalien ok sir I will try |
@cyberalien it worked, thank you so much sir! |
Same here. Don't know when this started as I don't watch the whole build process. These didn't work:
Sharing my info just in case it helps with the debugging. node: v20.11.1 Errors(getting like 500 errors like this on pnpm build, not just for iconify but for almost all the packages):
package.json:
|
Issue similar to Iconify/iconify#283 exists. Also, for Nuxt I recommend using |
Me too.But it doesn't seem to affect the program's operation |
Can anyone send a minimal reproduction so I can have a deeper look? |
@antfu here is the repro: https://github.com/ojvribeiro/nuxt-repro-deprecation-warning It is a fresh Nuxt project and Nuxt Icon is the only module installed. When I run the build command the Deprecation Warning message is spammed: |
That reproduction doesn't show any warnings when running build command on MacOS or Linux. Looking at this screenshot and previous screenshots, all reports use |
Actually, no, I have the similar issue on MacOS:
Seems like an issue is only with the |
Can you post a reproduction? |
Same issue here Running |
On Windows? |
Yes, sorry, on windows
…On Thu, Aug 1, 2024 at 11:11 AM Vjacheslav Trushkin < ***@***.***> wrote:
Same issue here
Running node 20.16.0 nuxt 3.12.3 @nuxt/icon 1.4.3
On Windows?
—
Reply to this email directly, view it on GitHub
<#140 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJTQKTDEUJCAOHDQ3MUMUDZPJT2VAVCNFSM6AAAAABC6JNWGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTGU2TKNBUHE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
i have same issue, |
Sorry, but not for now. Had this in issue in a private project with many dependencies. Probably, will share a reproduction if the problem will remain and I'll have more time to investigate. |
I was "trying" to find a fix for this. My current test env,. is latest nuxt + latest vueuse .
I'm seeing the issue also happening only starting from Nitro 2.6.0 ( ie downgrading to 2.5.2 will prevent the error to show up ) , not the best option since for example there's not ESM WASM support. So not sure if this is totally related to Nuxt part or Nitro at all.
Also not only DEP0166 is triggered also the DEP0155. may be it related at some poting to unjs/nitro#2523 ? |
Hello guys, by all my test:
I confirm the issue is only on Windows, after windows I tried Ubuntu and everything worked without changes |
Running
It happens only on windows while on macos it builds perfectly fine. |
Just in case anyone comes across this and wants to suppress the errors, you can prepend you script in your package.json with this under Windows until the bug is fixed:
cross-env would be the better choice for cross platform, but this is just temporary until the cause was found. |
was this issue fixed? |
When building my Nuxt.js project which uses this package, I get a bunch of deprecation warnings, following this format:
This looks to be referring to this line in the Iconify package.json:
https://github.com/iconify/iconify/blob/a8e3b45ecd56e194fd8ef2c3b4eeb6f8c4e68bb1/components/vue/package.json#L27
Have I got a configuration issue, or is this a bug in this library or the Iconify one?
Haven't found any previous reports of this, so this could just be an issue with my project.
I'm on Node v18.17.0, Nuxt v3.8.0 and NuxtIcon v0.6.1
Thanks :)
The text was updated successfully, but these errors were encountered: