[Vite] Add note info: peerDependency requirement

[ryuujo1573]

Type conflicts can be caused by installing rollup with version >=3 as peer dependency unconsciously.

Possible prevention of #2105

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
mdx	✅ Ready (Inspect)	Visit Preview	Nov 24, 2022 at 1:30PM (UTC)

[wooorm]

I think this is about pnpm + vite.
If pnpm doesn’t install peers for you, that’s fine, but we allow v2 and v3 of rollup as peers.
If vite wants a specific version, that’s on them.

I don’t think it’s worth it to maintain a list of which versions of Rollup that Vite supports here?

[ryuujo1573]

I'm aware now that this is about pnpm + vite.

I don’t think it’s worth it to maintain a list of which versions of Rollup that Vite supports here?

Yes, bing is my friend, nevertheless it would be nice for newbees who might use this directly with vite + pnpm, which reduces some problem.

Since vite was mentioned here, I might say that this tip provided as "possible conflicts" is of help? And this might not change unless vite to use rollup@3?
Just some ameteur opinions, please feel free to close this as won't-fix~

Thank you 🎵

[wooorm]

nevertheless it would be nice for newbees who might use this directly with vite + pnpm, which reduces some problem.

I think it’s inevitable that beginners will run into problems when trying to combine:

a) a pretty new rapidly developing package manager that does thing differently from how everything else works (pnpm)
b) a pretty new rapidly developing build tool that does thing different from how everything else works (Vite)
c) a best-effort type system (typescript)
d) anything else (mdx)

This is a problem with you not yet knowing how versions of packages work together (semver). How to install a previous version that some package wants instead of the latest. How to read pnpms error messages. How to silence a TS error. You will run into similar problems with any other tool.

That’s fine, totally understandable, and you’ll learn all that! But I think our docs will get worse for a lot of people if we try to answer all your questions in them.

I might say that this tip provided as "possible conflicts" is of help

This is a problem for a small number of users.
Such a section is also hard to maintain: it means that I need to check Vite’s docs every month or so to see if they support Rollup 3 or not.
There is also the problem that we already have a lot of docs. It can get overwhelming. It needs to be succinct.

---

Now. The root of this, is that Vite (currently at v3) wants you to install Rollup 2. And Vite v4 will support Rollup 3. We can say that succinctly:

<Note type="info">
  **Note**: Vite 3 (current) requires the older `rollup@2`.
  Vite 4 (beta) supports `rollup@3`.
</Note>

[ryuujo1573]

Thanks a lot!
I'm now getting used to the abcs of docs maintainence. 🤔
hmmmm, I was wondering if it would be fine to open the PR like this.

I will learn to contribute smartly, and please let me express my appreciation once again for your clear explanation and instruction.
Yeeee.

[codecov-commenter]

Codecov Report

Base: 100.00% // Head: 100.00% // No change to project coverage 👍

Coverage data is based on head (78ea076) compared to base (2635caf).
Patch has no changes to coverable lines.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #2180   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines         2050      2050           
=========================================
  Hits          2050      2050           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[wooorm]

Thank you, @ryuujo1573!!