-
Notifications
You must be signed in to change notification settings - Fork 32
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
Issues with peer dependencies #214
Comments
BTW, there seem to be a lot of outdated dependencies. Any reason not to bump them, or just have no time? |
Hi, I was on vacation, planning to update dependencies later on. There are some incompatibilities related with changes in the way Vite 4 handles ESM, but there should be a way to workaround those. |
Any chance that the dependencies could get updated? I'm fine even if iles itself stops gaining new features, but I hope that at least the dependencies can be up-to-date. There has been too long since the last update, so I can understand the difficulty to do this. I'd like to help if needed, but I'm not sure how to detect compatibility problems and ensure that everything works fine after upgrading the dependencies. |
Hi @ouuan! Doing batch upgrades every now and then is more efficient for me, as otherwise updating dependencies becomes a very time consuming chore. Primarily, there wasn't a compelling enough reason to update deps given that îles was working properly, but Vite 4.3 has some potential performance improvements that would benefit îles users, and that's a nice motivation. Thanks for reaching out, and stay tuned 😃 |
I think when a batch upgrade contains breaking changes, it's harder to locate where it breaks, so it's easier to keep the dependencies up-to-date continuously 🤔 I wrote the previous comment because I was not able to use the TypeScript 5 array extends syntax whose support was added in Vite 4.2. It's not very important though. |
Agreed, but it's a balancing act. In the case of Vite, which acts as a platform for this library, given îles is making use of most of its features—some in very specific ways—upgrading always has the risk of uncovering new bugs (both in Vite and îles). Without enough time to test, these bugs will be caught by îles users instead. Releasing less frequently allows me to spend more time testing manually in my sites when I do a release, resulting in îles users getting more stable experience, both when they upgrade or try it for the first time through |
Good day Max! With latest update to 0.9.5 & also create-iles package as well, any plans to update peer dependencies of @islands packages? I'm using feed and getting the peer dependencies error. Thanks. |
Hi, @ElMassimo! There has been a month since the release of Vite 4.3. Any plans to update the dependencies? |
Sorry, big life changes. Preparing a release targeting Vite 4.4. |
Awesome, can't wait 😀 |
@ElMassimo What's the status of 86ea918? Could you please test the latest Vite 4.4 and make a new iles release? |
iles
andvite
.Description 📖
After bumping the dependencies, issues with peer dependencies are found by pnpm.
I think
@islands/feed
needs to update the peer dependency version andiles
needs to bump its dependencies.Reproduction 🐞
Run
ncu
,pnpm i
andpnpm typecheck
in https://github.com/ouuan/iles-blog.pnpm i
shows:(see edit log) It turns out that the type check error was caused by https://github.com/doesdev/rollup-plugin-analyzer not specifying rollup version inpnpm typecheck
shows:package.json
and using rollup 2, which is not related to iles, and the peer dependency warnings are harmless. But still love to see updated dependencies with the peer dependency warning resolved :)Dependencies Info
Run
npx iles info
andpnpm list
(ornpm list
) and provide the output:The text was updated successfully, but these errors were encountered: