You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the ViteDevServer interface is awkwardly explained in a single code block with a large TypeScript interface type and JavaScript comment blocks.
In addition, the methods appear to be under-specified.
For example, nowhere is the originalUrl argument of transformIndexHtml explained. Why does it need to be defined and not equal to "/" before relative <script> dependencies can have their src attribute transformed?
I believe the formatting of the current ViteDevServer documentation is unwelcoming to further clarification.
Your Suggestion for Changes
It would make more sense for ViteDevServer to have its own page, with each property/method described in Markdown with individual code examples.
Reproduction
No response
Steps to reproduce
No response
The text was updated successfully, but these errors were encountered:
hey, @aleclarson. i'd be glad if you could add some info on how and where to add the page. this would really help me complete the task if no one’s taken it on yet
Documentation is
Explain in Detail
Currently, the
ViteDevServer
interface is awkwardly explained in a single code block with a large TypeScriptinterface
type and JavaScript comment blocks.In addition, the methods appear to be under-specified.
For example, nowhere is the
originalUrl
argument oftransformIndexHtml
explained. Why does it need to be defined and not equal to"/"
before relative<script>
dependencies can have theirsrc
attribute transformed?I believe the formatting of the current
ViteDevServer
documentation is unwelcoming to further clarification.Your Suggestion for Changes
It would make more sense for
ViteDevServer
to have its own page, with each property/method described in Markdown with individual code examples.Reproduction
No response
Steps to reproduce
No response
The text was updated successfully, but these errors were encountered: