npmpackage.info

@wordpress/stylelint-config

The Block Editor project for WordPress and beyond. Plugin is available from the official repository.

23.5.0

10,545

NOASSERTION

JavaScript

7,100,343 5.7

Installations

npm install @wordpress/stylelint-config

Pull Requests

Open

1,407

Total

37,624

Closed

6,547

Merged

29,670

Issues

Open

6,049

Total

28,876

Closed

22,827

Releases

541

19.8.0 RC1

v19.8.0-rc.1

Published on 27 Nov 2024

19.7.0

v19.7.0

Published on 20 Nov 2024

19.6.4

v19.6.4

Published on 18 Nov 2024

19.6.3

v19.6.3

Published on 18 Nov 2024

19.7.0 RC2

v19.7.0-rc.2

Published on 14 Nov 2024

19.6.2

v19.6.2

Published on 14 Nov 2024

View all 541 releases

Developer

WordPress

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

>=18.12.0

Typescript Support

No

Node Version

20.18.1

NPM Version

lerna/7.1.4/node@v20.18.1+x64 (linux)

Statistics

10,545 Stars

34,403 Commits

4,217 Forks

348 Watching

2,895 Branches

1,291 Contributors

Updated on 27 Nov 2024

Languages

JavaScript (62.34%)

TypeScript (16.9%)

PHP (11.1%)

HTML (3.73%)

SCSS (3.6%)

Java (1%)

Swift (0.6%)

Kotlin (0.2%)

Mustache (0.13%)

Shell (0.11%)

CSS (0.09%)

MDX (0.09%)

Objective-C (0.04%)

PEG.js (0.04%)

Ruby (0.03%)

Total Downloads

Cumulative downloads

Total Downloads

7,100,343

Last day

-1.8%

13,697

Compared to previous day

Last week

0.2%

64,298

Compared to previous week

Last month

14.2%

267,958

Compared to previous month

Last year

74.8%

3,452,104

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

@stylistic/stylelint-plugin stylelint-config-recommended stylelint-config-recommended-scss

Peer Dependencies

stylelint

Versions

Gutenberg

Screenshot of the Gutenberg Editor, editing a post in WordPress

Welcome to the development hub for the WordPress Gutenberg project!

"Gutenberg" is a codename for a whole new paradigm in WordPress site building and publishing, that aims to revolutionize the entire publishing experience as much as Gutenberg did the printed word. Right now, the project is in the second phase of a four-phase process that will touch every piece of WordPress -- Editing, Customization, Collaboration (which includes Real-time collaboration, Asynchronous collaboration, Publishing flows, Post revisions interface, Admin design, Library), and Multilingual -- and is focused on a new editing experience, the block editor.

The block editor introduces a modular approach to pages and posts: each piece of content in the editor, from a paragraph to an image gallery to a headline, is its own block. And just like physical blocks, WordPress blocks can be added, arranged, and rearranged, allowing WordPress users to create media-rich pages in a visually intuitive way -- and without work-arounds like shortcodes or custom HTML.

The block editor first became available in December 2018, and we're still hard at work refining the experience, creating more and better blocks, and laying the groundwork for the next three phases of work. The Gutenberg plugin gives you the latest version of the block editor, so you can join us in testing bleeding-edge features, start playing with blocks, and maybe get inspired to build your own.

Check out the Keeping up with Gutenberg Index

Getting Started

Get hands on: check out the block editor live demo to play with a test instance of the editor.

Using Gutenberg

Download: To use the latest release of the Gutenberg plugin on your WordPress site: install from the plugins page in wp-admin, or download from the WordPress.org plugins repository.
User Documentation: See the WordPress Editor documentation for detailed docs on using the editor as an author creating posts and pages.
User Support: If you have run into an issue, you should check the Support Forums first. The forums are a great place to get help. If you have a bug to report, please submit it to the Gutenberg repository. Please search prior to creating a new bug to confirm it's not a duplicate.

Developing for Gutenberg

Extending and customizing is at the heart of the WordPress platform, this is no different for the Gutenberg project. The editor and future products can be extended by third-party developers using plugins.

Review the Quick Start Guide for the fastest way to get started extending the block editor. See the Block Editor Handbook for extensive tutorials, documentation, and API references. Also, check the WordPress Developer Blog for great articles about block development, among other topics.

Contribute to Gutenberg

Gutenberg is an open-source project and welcomes all contributors from code to design, and from documentation to triage. The project is built by many contributors and volunteers, and we'd love your help building it.

See the Contributors Handbook for all the details on how you can contribute.

To get up and running quickly with code contribution see Getting Started With Code Contribution. Also check out the other resources available on the Code Contributions page.

In whichever way you wish to contribute please be sure to read the Contributing Guidelines first.

As with all WordPress projects, we want to ensure a welcoming environment for everyone. With that in mind, all contributors are expected to follow our Code of Conduct.

Get Involved

You can join us in the #core-editor channel in Slack, see the WordPress Slack page for signup information; it is free to join.

License

WordPress is free software, and is released under the terms of the GNU General Public License version 2 or (at your option) any later version. See LICENSE.md for complete license.

Code is Poetry.

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Packaging

Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

9

Security-Policy

Determines if the project has published a security policy.

9

License

Determines if the project has defined a license.

8

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Signed-Releases

Determines if the project cryptographically signs release artifacts.

0

SAST

Determines if the project uses static code analysis.

0

Fuzzing

Determines if the project uses fuzzing.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

5.7

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More

Other packages similar to @wordpress/stylelint-config

stylelint-config-recommended

14.0.1

Recommended shareable config for Stylelint

stylelint-config-recommended-scss

14.1.0

The recommended shareable SCSS config for Stylelint

@wordpress/browserslist-config

6.13.0

WordPress Browserslist shared configuration.

stylelint-scss

6.10.0

A collection of SCSS-specific rules for Stylelint