Peter

maybe related to https://github.com/nuxt/nuxt/discussions/16716

unfortunately not :/ @danielroe @pi0 can you have a look ?

@pi0 any news on that ? Can we might just disable the warning.

@pi0 thanks for the feedback and it's great to hear you are working on a better release cycle. I am aware of the edge channel. However, this always requires resetting...

> > However, this always requires resetting the node_modules folder and the package-lock.json file and i would like to avoid this. > > This is the same recommendation for all...

good to know. Haven't use pnpm yet ^^ :sweat_smile:

@pi0 any news ? It has been months in the meantime since the last release :pensive:

@BenRacicot the error is really strange. Can you do me a favor and check: 1. if the error persists with node version 18.x? 2. if the error persists with node...

PS: thanks for sponsoring :heart:

damm. i was hoping that it was due to the exports for the bin directory. Are you using the latest version of ts-node ?