feat(docs): add loaders and plugins index pages#153
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
also one thing - the API links use a hardcoded v5.x (same as the footer already does), so they're consistent for now. but after webpack 6 lands, these will need a quick find-n-replace, or better will be , a /docs/api/latest alias so we don't have to keep updating them every major version |
Can you add them to those links? |
|
Sure, will be adding those. |
|
Sorry for the delay , i added those plugins and loaders pointing to the index , but there are some plugins like SplitChunksPlugin, DefinePlugin, etc but they exist as the output of the typedoc pipeline , the old anchors wouldnt resolve here if i point to the api pages , so what we should do here ? aany suggestions or should we point it to the API pages |
|
fixed the source from the frontmatter , also should we point the plugins mentioned above to the API docs or leave it as a TODO for now ? |
| | [`SvgChunkWebpackPlugin`](https://www.npmjs.com/package/svg-chunk-webpack-plugin) | Generate SVG sprites optimized by SVGO based on your entry point dependencies | | ||
| | [`MinimizerPlugin`](/docs/plugins/minimizer-webpack-plugin) | Uses Terser (or other) to minify the JS/CSS/HTML/JSON/etc in your project | | ||
|
|
||
| For more third-party plugins, see the list from [awesome-webpack](https://github.com/webpack-contrib/awesome-webpack#webpack-plugins). |
There was a problem hiding this comment.
Let's remove this line, we are still working on a new home for these
|
I think we need to re-write these files from scratch, since they don't properly articulate what we want them to, that these directories are for first-party external plugins/loaders. I'll rewrite the files, unless you want to? |
|
Sure , no problem I am open to both , you may write it or you can guide me over it , also should i close this PR then |
2 participants
This adds the loaders and plugins index pages, so
/docs/loadersand/docs/pluginsfinally point to real landing pages instead of dead links (the footer already linked to them). I copied the content over from webpack.js.org and fixed up the links: our own loaders/plugins point to their local pages, built-in plugins point to their API docs, and the third-party ones keep their npm/GitHub links.This also unblocks the
#TODO[/loaders]and#TODO[/plugins]markers in the guides from #147, since they now have somewhere to go.