fix: ignoreWarnings not working on webpack 5

[ImLunaHey]

if this PR isn't wanted im happy to maintain my own fork. 🙏

also im not 100% how to fix the error the tests are throwing. 🤔
if someone can point me in the right direction ill be happy to fix them up.

closes: #90 and #81

[RoccoC]

This is great, thank you!

A few considerations:

• technically this is a breaking change since the plugin will no longer work with webpack versions < 5, so we should bump the version to 3.0.0
• the failing test is due to changes in the postcss-loader config API, but after fixing this I found that the original test case is no longer valid for webpack 5 and the latest version of autoprefixer. I think it's best to remove the Should handle warning from child compiler test case from tests/test.spec.ts, as well as any related files that are no longer needed for the test (tests/childWarning.js, tests/test.css). This means we can also remove the css loaders/plugins from tests/webpack.config.ts and package dependencies, too.
• I know that TSLint is long deprecated, but I think it would be great to replace it with ESLint (or at least keep it around until we do).

Thanks again! 🙏

[ImLunaHey]

Let me get this fixed up. 🙏

[ImLunaHey]

@RoccoC let me know if that resolves all the issues. 🙏

[ImLunaHey]

bump ⬆️

[RoccoC]

bump ⬆️

There's an issue when running npm test, but otherwise all looks good! Thanks again, and so sorry for the delay!

[ImLunaHey]

if tests need to pass before merging then a CI action should be added to enforce that.

[ImLunaHey]

i cannot get the tests to run locally. they just sit there without doing anything.

➜  webpack-build-notifier git:(master) ✗ npm run test -- --verbose

> webpack-build-notifier@3.0.0 test
> jest --verbose


 RUNS  tests/test.spec.ts

[RoccoC]

i cannot get the tests to run locally. they just sit there without doing anything.

I'll get these fixed up and merged. Thanks for your PR.

[RoccoC]

if tests need to pass before merging then a CI action should be added to enforce that.

Thanks for flagging this. Looks like TravisCI was no longer working. I went ahead and migrated to CircleCI.

[ImLunaHey]

@RoccoC kinda an odd move to repush this as your own commit and wipe me from the authors...

[RoccoC]

@RoccoC kinda an odd move to repush this as your own commit and wipe me from the authors...

Ah crap, @ImLunaHey , this was completely unintentional. I had first merged your PR into a new branch so I could fix the test issues, but when I merged that branch into master I didn't consider that all the work would be misattributed to me. 🫤

Interestingly, the auto-generated release notes captured your contribution.

I apologize for messing this up. Let me see if I can amend the commit history.

[chadlwilson]

Seems a bit unusual, generally if one rebases and rewrites history the "author" is retained, just committer changes. Think you'd probably need to rewrite history and force push on master to fix that for @ImLunaHey :-(

[RoccoC]

Think you'd probably need to rewrite history and force push on master to fix that

Exactly, thanks! 😄

@ImLunaHey , thanks again for the contribution, and apologies for my screw-up here

[chadlwilson]

(Sorry I ended up here because I posted a stupid question about whether this broke Webpack 4 compat, but saw up above that it does so deleted my comment - also see the release notes were clarrified that Webpack 4 support/compat was dropped so thank you for that!)

[RoccoC]

Ha, no worries! I was looking for that comment so I could reply 🙂

[chadlwilson]

Also thank you for putting in the effort to correct the contrib history here. It can seem like a small thing, but personally I feel these such small things are really important for the vibe/culture of OSS, especially now LLMs are laundering all our contributions everywhere else. It's a thankless task at the best of times! 😬

[ImLunaHey]

[ImLunaHey]

gg git 😅