docs(plugins): remove all depreciated plugins

[snitin315]

Fixes #3775

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/webpack-docs/webpack-js-org/1m7ifo5g0
✅ Preview: https://webpack-js-org-git-fork-snitin315-docs-plugins.webpack-docs.vercel.app

[snitin315]

/cc @evilebottnawi

[alexander-akait]

Good job!

[EugeneHlushko]

Approving, there is room to imrpove in another PR if you are willing to take on it

[EugeneHlushko]

Actually, you need to cleanup a link:

✖ FAIL load dist/plugins/extract-text-webpack-plugin
  | operator: load
  | expected: 200 dist/plugins/extract-text-webpack-plugin
  |   actual: ENOENT: no such file or directory, open '/home/travis/build/webpack/webpack.js.org/dist/plugins/extract-text-webpack-plugin/'
  |       at: dist/plugins/mini-css-extract-plugin/index.html:316:29 <a href="/plugins/extract-text-webpack-plugin/">...</a>

[snitin315]

@EugeneHlushko Can you guide me for same?
This link seems to be inside plugins/_mini-css-extract-plugin which is being ignored by git?

[montogeek]

@snitin315 dist/plugins/extract-text-webpack-plugin doesn't exist anymore because this same PR deletes it.
Yes, file is ignored by git but still it is deployed, which mean you will need to remove it from mini-css-extract-plugin own README file.

[EugeneHlushko]

✖ FAIL load dist/plugins/extract-text-webpack-plugin
  | operator: load
  | expected: 200 dist/plugins/extract-text-webpack-plugin
  |   actual: ENOENT: no such file or directory, open '/home/travis/build/webpack/webpack.js.org/dist/plugins/extract-text-webpack-plugin/'
  |       at: dist/loaders/extract-loader/index.html:10:53 <a href="/plugins/extract-text-webpack-plugin/">...</a>

[alexander-akait]

/cc @snitin315 @EugeneHlushko @montogeek What is status? Maybe I can help?

[snitin315]

Need to merge peerigon/extract-loader#87

[alexander-akait]

I'm afraid it will never be merged, what is our workaround?

[snitin315]

Need to investigate why our linting depends on other repositories readme files. /cc @montogeek

[alexander-akait]

/cc @webpack/documentation-team friendly ping, developers still follow outdated projects and ask me why loaders/plugins are outdated, how I can help

[alexander-akait]

/cc @EugeneHlushko friendly ping too

[montogeek]

We could skip this link in particular.

[alexander-akait]

@montogeek Can you take care about it? Thanks!

[alexander-akait]

@montogeek @EugeneHlushko Please start to solve this issue ASAP, I get questions and error messages every day and it wastes my time

[chenxsan]

@snitin315 Could you try to update "lint:links" script in packages.json to this?:

"lint:links": "hyperlink -c 8 -r dist/index.html --canonicalroot https://webpack.js.org/ -i --skip /plugins/extract-text-webpack-plugin/ --skip https://img.shields.io --skip **/printable** --skip https://david-dm.org --skip https://codecov.io/gh --skip 'content-type-mismatch https://travis-ci.org' > internal-links.tap; cat internal-links.tap | tap-spot"

I've added this --skip /plugins/extract-text-webpack-plugin/ to skip it.

It fixed the CI failure in my test locally.

[snitin315]

Thanks @chenxsan I will update.

[chenxsan]

The current issue was gone as far as I see. Now there's another problem coming from source-map-loader:

  ✖ FAIL fragment-check dist/loaders/source-map-loader/index.html --> #url
  | operator: fragment-check
  | expected: id="url"
  |       at: dist/loaders/source-map-loader/index.html:1:14330 <a href="#url">...</a>

I've already submitted a pull request there webpack-contrib/source-map-loader#126, hopefully we can get the CI fixed soon once it is merged.

[snitin315]

Can we skip all the /plugins/** & /loaders/** links?

[chenxsan]

@snitin315 CI should pass now if you rerun it.

[chenxsan]

I think lint:links script is good at catching those potential broken links. The problem here is we lint third-party plugins/loaders too, which might block CI if pull requests can't be merged there.

[alexander-akait]

Thanks!

[EugeneHlushko]

Yup it works now, indeed its hard given that readmes are outside of our codebase in webpack.js.org repo, but serving broken links never works well, thats why it was decided to keep it at error level, nobody would care if it was a warning

[EugeneHlushko]

Thanks!