Prepare 15.0.0

[jeddy3]

• Remove Node.js 12 support #6311
• Remove support for processors #3408
• Deprecate stylistic rules handled by Prettier #6342
• Remove deprecated syntax option #6414

Discussed:

• Create the 8-rules plugin (for the ones not yet handled by Prettier) #6483

Pull requests:

• Change extends in overrides to be consistent with plugins behaviour #6380
• Bump postcss-import from 14.1.0 to 15.0.0 #6323
• Bump jest from 28.1.3 to 29.0.2, jest-preset-stylelint from 5.0.4 to 6.0.0 #6332

There's no fixed date for when this might happen. We'll need to investigate what's possible and what we've time to do.

This is an umbrella issue for tracking our progress and for broad discussions. Let's use the individual issues for specific discussions.

Ref: Some initial discussion in #6311.

[ybiquitous]

@jeddy3 Thanks for listing up the tasks.

It seems we can remove the deprecated syntax option. Is there a related issue?

stylelint/types/stylelint/index.d.ts

Lines 243 to 244 in d402889

	/** @deprecated Use `customSyntax` instead. Using this option will result in an error. */
	syntax?: string;

[jeddy3]

It seems we can remove the deprecated syntax option.

I agree.

Is there a related issue?

I don't believe so. Let's create one.

[ybiquitous]

Thanks. I've opened #6414 and updated this issue description.

---

EDIT: If further context is necessary, please feel free to add it to the description of #6414.

[ybiquitous]

I've created the v15 branch just now. Let's push all the breaking changes into the branch.

[ybiquitous]

I've cleaned up some tasks. Thank you for your reviews, @jeddy3.

The ESM task is the biggest, so I believe it's recommended to work on the task after reducing the code as possible.

[Mouvedia]

If the rules are dropped and not just deprecated, I think #6483 should be added to the list of the blocking issues.

[ybiquitous]

I've added #6483 to the list above.

[ntwb]

⭐ Stylelint hit 10,000 stars this weekend

[jeddy3]

@ybiquitous The ESM task is the biggest, so I believe it's recommended to work on the task after reducing the code as possible.

Yes, I agree that the ESM task is extensive and we'll want to reduce the code first.

I suggest we move the ESM task to v16. I think dropping support for node 12 and deprecating a lot of stylistic rules is enough for this major release.

In a few months, we can release v16 to:

• remove the rules we deprecate in v15
• migrate to ESM

That way we'll allow the:

• dust to settle on the rule deprecations
• migration of a smaller code base to ESM

What do you think?

[ybiquitous]

I suggest we move the ESM task to v16.

Good idea! 👍🏼

[ybiquitous]

Left tasks:

• Reorganize type definitions #6510
• Add declaration-property-value-no-unknown #6511

[ybiquitous]

Packages status for 15.0.0

based on npmjs.com search

Name	PR	Status
stylelint-config-recommended	#180	✅
stylelint-config-standard	#277	✅
stylelint-order	#1 (fork)	✅
stylelint-config-prettier	#1 (fork)	✅
stylelint-scss	#1 (fork)	✅
stylelint-config-idiomatic-order	#1 (fork)	✅
stylelint-webpack-plugin	#311	❌ (failed with v14.16.0)
stylelint-config-recommended-scss	#1 (fork)	✅
stylelint-config-standard-scss	#1 (fork)	✅
stylelint-config-sass-guidelines	#1 (fork)	✅
stylelint-no-unsupported-browser-features	#1 (fork)	✅
stylelint-prettier	#1 (fork)	✅
stylelint-config-css-modules	#1 (fork)	✅
stylelint-config-recess-order	#1 (fork)	✅
stylelint-declaration-block-no-ignored-properties	#1 (fork)	✅
stylelint-config-recommended-vue	#1 (fork)	✅
stylelint-config-html	#1 (fork)	✅

[jeddy3]

@ybiquitous Great job getting everything prepared! I'd like to give the documentation a once-over before we release 15.0.0 to clearly communicate to our users the direction Stylelint is going in. It's the holiday season here, but I hope to find time in the next week or so to do this.

[ybiquitous]

@jeddy3 Thank you. I'll test packages depending on Stylelint as long as time permits.

[hudochenkov]

Folks, did you consider deprecate support of Node.js 14 in v15? Node.js 14 end of life is on 2023-04-30.

[ybiquitous]

Oh, we have four months left! 😳 But I think dropping v14 is challenging because many packages still support v14.

[jeddy3]

Folks, did you consider deprecate support of Node.js 14 in v15?

Let's drop it in v16.

I'd like to give the documentation a once-over

(FYI, I'll hopefully have the v15 docs done in a few days.)

[jeddy3]

We're not far off from being ready to release 15.0.0.

We need to get this two pull requests in:

• Add deprecated rule warnings #6561
• Prepare 15.0.0 docs #6573

Then I'll resolve the conflicts and address suggestions in:

• Add declaration-property-value-no-unknown #6511

We can then decide if we want to include that rule or not.

We'll also want to add deprecating postcss-css-in-js to our release steps as it's tied in the removed processors config property.

I should have time over the coming weeks to help see the release through.

[henryruhs]

What about a 15.0.0.next-1 release so plugin authors can pre-check it? I would love to test the ESM compatibility as this is a blocker for me to move to a modern codebase.

[jeddy3]

What about a 15.0.0.next-1 release so plugin authors can pre-check it?

Sure, no harm in a pre-release. It'll also make it easier for us all to test against our CSS codebases.

I would love to test the ESM compatibility as this is a blocker for me to move to a modern codebase.

I don't believe there's anything in 15.0.0 that changes ESM compatibility. The changes we're making (removing the processors config property, deprecating stylistic rules, etc) are a stepping stone to let us better assess if migrating to ESM (#5291) is viable. It'll be a large undertaking.

[ybiquitous]

We'll also want to add deprecating postcss-css-in-js to our release steps as it's tied in the removed processors config property.

Agreed 👍🏼

What about a 15.0.0.next-1 release so plugin authors can pre-check it?

No objections. We can also try the pre-released code by installing the v15 branch directly from the GitHub repo:

npm install "github:stylelint/stylelint#v15"

[ybiquitous]

Close via #6573

The last one toward v15 should be #6425.

[jeddy3]

The last one toward v15 should be #6425.

And #6511.

[ybiquitous]

And #6511.

Sorry, I missed it. I'll check it.