chore: bump detective-postcss to v6

[PabloLION]

Why

When installing madge with yarn and node v18.2.0. This error was thrown

error detective-postcss@5.1.1: The engine "node" is incompatible with this module. Expected version "12.x || 14.x || 16.x". Got "18.2.0"

How

I tried yarn install in a fork of this repo and it had the same error.
After yarn update detective-postcss@latest, there's no more error on yarn install and yarn test still passes.
Please consider merge this PR (and better, add some dependency checker in this code base).

TIA

[fdc-viktor-luft]

This update is required for Node 18 support

[fdc-viktor-luft]

Why don't get approved PRs not get merged here? @kkamik or @PabloLION can't you merge this and release a new version? Also other good PRs are pending a long time. What is the reason?

[PabloLION]

Hi @fdc-viktor-luft . This repo is still under maintenance (by @pahen, and I'm not authorized to merge) since new PRs like #325 are still getting merged.
Personally I don't think creating a fork for only one PR is a very good idea. Maybe we can ask @pahen if there's anything wrong? I didn't test if this breaks node 14 support so more works needs to be done.

To me the fork is needed only when maintainers have very different (and absurd to me) expectations of this repo like "We only want to keep this available for node 11". If so, I'll publish a new NPM package.

[PabloLION]

and adopt this project. I think this tool helped a lot!

[pahen]

Why don't get approved PRs not get merged here? @kkamik or @PabloLION can't you merge this and release a new version? Also other good PRs are pending a long time. What is the reason?

I’m on paternity leave until January 2023 and building a new house so there’s no time to maintain this project right now 😢 I’ll see if I can get help maintaining this project. Any suggestions?

[fdc-viktor-luft]

@pahen That can happen. Don't worry. We just need someone else who can take care instead of you. Maybe you share write access to someone who volunteers.

I will be on parental leave soon, too. Will be back on February 2023, but I can offer to take care of smaller tasks. I'm maintaining and own also several npm packages, but none so popular for sure.

@PabloLION wants to volunteer maybe too? 😅

[PabloLION]

@pahen @fdc-viktor-luft yea sure. Just to be clear I have no experience maintaining any popular package like this one. I'm currently between jobs. I'll try my best until I become busy again, but I'm sure that'll be after January 2023.

[PabloLION]

I've posted a new issue #334 to discuss about the new topic in order to keep the discussion here focused on this PR.

[StanislavKharchenko]

Any updates?
This stop to switch to Node 18

[fdc-viktor-luft]

Sadly not. If you're using e.g. pnpm you can use this in your package.json as current workaround in order to use Node 18:

{
  "pnpm": {
    "overrides": {
      "detective-postcss": "6.1.0"
    }
  }
}

[kamiazya]

LGTM!