add r/webpack page#5196
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/webpack-docs/webpack-js-org/A3wjw23KTAQfn2pu9HhAggc3FrTi |
| @@ -12,8 +12,9 @@ export default function (location) { | |||
|
|
|||
| if (location.pathname === '/webpack-options/') { | |||
There was a problem hiding this comment.
Maybe /webpack/options/ so in future we will add /webpack-dev-server/options/ and maybe more
There was a problem hiding this comment.
How about https://webpack.js.org/webpack/?option=output/filename https://webpack.js.org/webpack-dev-server/?option=xxx? It's more terse.
Or https://webpack.js.org/r/webpack/?option=output/filename which is more future proof in case we will be using /webpack/ path on this site in future.
|
I'm afraid these's no one-size-fits-all solution as the documents don't share a common pattern. E.g.,
This pull request would work only for the first pattern. And there could be other patterns besides the aforementioned two. Anyway we can maintain a redirect map like below on this repository: {
'output/filename': '/configuration/output/#outputfilename',
}But I don't think it's a good idea, there could be hundreds of options. Generally I think we should just let users take advantage of the search function on our documentation site. |
|
Stale |
An experiment for webpack/webpack#13822 (review)
https://webpack.js.org/r/webpack/?option=output/filenamehttps://webpack.js.org/configuration/output/#outputfilenameCurrently we can only make those redirections happen on client side as a single page application hosted on github pages won't support any server side redirects, i.e., urls of
https://webpack.js.org/webpack-options/output/chunk-load-timeouttype won't work unless we generate every intermediate page for them.Example: https://webpack-js-org-git-fork-chenxsan-feature-ha-97c6dc-webpack-docs.vercel.app/r/webpack/?option=output/filename