create-docusaurus 0.0.0-4377 → 0.0.0-4384

package/templates/facebook/node_modules/stylelint/CONTRIBUTING.md

@@ -0,0 +1,81 @@
+# Contributing
+
+Thank you for wanting to contribute.
+
+To help out, you can:
+
+- get involved in any open [issue](https://github.com/stylelint/stylelint/issues) or [pull request](https://github.com/stylelint/stylelint/pulls)
+- improve our [support for non-standard syntaxes](docs/about/syntaxes.md)
+- create, enhance and debug rules using [our guide](docs/developer-guide/rules.md)
+- improve the [documentation](docs/)
+- add [new tests](https://github.com/stylelint/stylelint/issues?q=is%3Aopen+is%3Aissue+label%3A%22type%3A+tests%22) to _absolutely anything_
+- improve the [performance of rules](docs/developer-guide/rules.md#improve-the-performance-of-a-rule)
+- open [new issues](https://github.com/stylelint/stylelint/issues/new/choose) about your ideas for making stylelint better
+- create or contribute to [integrations](docs/user-guide/integrations/editor.md), like our plugin for [VS Code](https://github.com/stylelint/vscode-stylelint)
+
+Not only will you help stylelint thrive, but you may learn a thing or two — about CSS, PostCSS, Node, ES2015, unit testing, open-source software, and more. We want to encourage contributions! If you want to participate but couldn't, please [give us feedback](https://github.com/stylelint/stylelint/issues/new) about what we could do better.
+
+## Code contributions
+
+To start coding, you'll need:
+
+- a minimum of [Node.js](https://nodejs.org/en/) v10, though we do recommend using the latest LTS release
+- the latest [npm](https://www.npmjs.com/)
+
+Then:
+
+1. [Fork and clone](https://guides.github.com/activities/forking/) the stylelint repository.
+2. Install all the dependencies with `npm ci`.
+
+### Run tests
+
+Next, you'll want to run the tests using `npm test`.
+
+However, this runs all 25,000+ unit tests and also linting.
+
+You can use the interactive testing prompt to run tests for just a chosen set of files (which you'll want to do during development). For example, to run the tests for just the `color-hex-case` and `color-hex-length` rules:
+
+1. Run `npm run watch` to start the interactive testing prompt.
+2. Press `p` to filter by a filename regex pattern.
+3. Enter `color-hex-case|color-hex-length`, i.e. each rule name separated by the pipe symbol (`|`).
+
+You can find more information about testing on the [Jest website](https://jestjs.io/).
+
+### Write code
+
+With the interactive testing prompt running, you can write code confident that things are working as expected.
+
+You can write code to:
+
+- [add a rule](docs/developer-guide/rules.md#add-a-rule)
+- [add an option to a rule](docs/developer-guide/rules.md#add-an-option-to-a-rule)
+- [fix a bug in a rule](docs/developer-guide/rules.md#fix-a-bug-in-a-rule)
+- [improve the performance of a rule](docs/developer-guide/rules.md#improve-the-performance-of-a-rule)
+
+And many more things, including [writing system tests](docs/developer-guide/system-tests.md) and improving the [documentation](docs/).
+
+### Format code
+
+We use [Prettier](https://prettier.io/) (with [a Husky and lint-staged precommit](https://prettier.io/docs/en/precommit.html)) to format your code automatically.
+
+Alternatively, you can:
+
+- trigger the pretty-printing all the files using `npm run format`
+- use a [Prettier editor integration](https://prettier.io/docs/en/editors.html)
+
+### Open a pull request
+
+When you have something to share, it's time to [open a pull request](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork).
+
+After we review and merge your pull request, we'll invite you to become a maintainer of the stylelint organization. You'll then be able to help manage issues, pull requests and releases. You'll also be able to work on the stylelint repository rather than your fork.
+
+## Financial contributions
+
+We welcome financial contributions in full transparency on our [Open Collective](https://opencollective.com/stylelint).
+
+Anyone can file an expense. We will "merge" the expense into the ledger if it makes sense for the development of the community. Open Collective then reimburses the person who filed the expense.
+
+You can financially support us by becoming a:
+
+- [backer](https://opencollective.com/stylelint#backer)
+- [sponsor](https://opencollective.com/stylelint#sponsor)

package/templates/facebook/node_modules/stylelint/LICENSE

@@ -0,0 +1,20 @@
+The MIT License (MIT)
+
+Copyright (c) 2015 - present Maxime Thirouin, David Clark & Richard Hallows
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

package/templates/facebook/node_modules/stylelint/README.md

@@ -0,0 +1,48 @@
+# stylelint
+
+[![NPM version](https://img.shields.io/npm/v/stylelint.svg)](https://www.npmjs.org/package/stylelint) [![Build Status](https://github.com/stylelint/stylelint/workflows/CI/badge.svg)](https://github.com/stylelint/stylelint/actions) [![NPM Downloads](https://img.shields.io/npm/dm/stylelint.svg)](https://npmcharts.com/compare/stylelint?minimal=true)
+
+A mighty, modern linter that helps you avoid errors and enforce conventions in your styles.
+
+## Features
+
+It's mighty as it:
+
+- understands the **latest CSS syntax** including custom properties and level 4 selectors
+- extracts **embedded styles** from HTML, markdown and CSS-in-JS object & template literals
+- parses **CSS-like syntaxes** like SCSS, Sass, Less and SugarSS
+- has over **170 built-in rules** to catch errors, apply limits and enforce stylistic conventions
+- supports **plugins** so you can create your own rules or make use of plugins written by the community
+- automatically **fixes** the majority of stylistic violations
+- is **well tested** with over 15000 unit tests
+- supports **shareable configs** that you can extend or create
+- is **unopinionated** so that you can customize it to your exact needs
+- has a **growing community** and is used by [Facebook](https://code.facebook.com/posts/879890885467584/improving-css-quality-at-facebook-and-beyond/), [GitHub](https://github.com/primer/stylelint-config-primer) and [WordPress](https://github.com/WordPress-Coding-Standards/stylelint-config-wordpress)
+
+## Example output
+
+![Example](https://github.com/stylelint/stylelint/raw/master/example.png?raw=true)
+
+## Getting started
+
+You'll find steps to [get started in our User guide](docs/user-guide/get-started.md).
+
+## Contributors
+
+Without the contributions from [all these fantastic people](https://github.com/stylelint/stylelint/graphs/contributors), stylelint would not exist. [Become a contributor](CONTRIBUTING.md).
+
+## Backers
+
+<a href="https://opencollective.com/stylelint#backers" target="_blank"><img src="https://opencollective.com/stylelint/backers.svg?width=890"></a>
+
+Thank you to all our backers! [Become a backer](https://opencollective.com/stylelint#backer).
+
+## Sponsors
+
+<a href="https://opencollective.com/stylelint/sponsor/0/website" target="_blank"><img src="https://opencollective.com/stylelint/sponsor/0/avatar.svg"></a>
+
+Support this project to show your logo here with a link to your website. [Become a sponsor](https://opencollective.com/stylelint#sponsor).
+
+## License
+
+[The MIT License](https://raw.githubusercontent.com/stylelint/stylelint/master/LICENSE).

package/templates/facebook/node_modules/stylelint/bin/stylelint.js

@@ -0,0 +1,8 @@
+#!/usr/bin/env node
+
+'use strict';
+
+// to use V8's code cache to speed up instantiation time
+require('v8-compile-cache');
+
+require('../lib/cli')(process.argv.slice(2));

package/templates/facebook/node_modules/stylelint/docs/about/linting.md

@@ -0,0 +1,34 @@
+# Linting
+
+A linter is a tool that analyzes source code to flag programming errors, bugs, stylistic errors, and suspicious constructs.
+
+You can use a linter with a pretty printer and a validator. There are, however, usually overlaps between these three types of tools.
+
+## Pretty printers
+
+There are two approaches to enforcing stylistic conventions:
+
+- a machine algorithmically pretty prints the code (usually based on a maximum line length)
+- a human initially formats the code, and a machine fixes-up/warns-about any mistakes
+
+The former is handled by pretty printers, like [prettier](https://github.com/prettier/prettier), whereas the latter is catered for by the built-in [stylistic rules](../user-guide/rules/list.md#stylistic-issues). If you use a pretty printer, you'll want to use [`stylelint-config-recommended`](https://github.com/stylelint/stylelint-config-recommended), which only turns on [possible error](../user-guide/rules/list.md#possible-errors) rules.
+
+Additionally, the built-in stylistic rules and plugins are configurable to support a diverse range of stylistic conventions. For example, ordering properties within declaration blocks is a divisive topic, where there isn't a dominant convention. The [`stylelint-order`](https://www.npmjs.com/package/stylelint-order) plugin can be configured to lint and fix a diverse range of ordering conventions.
+
+Another example is the use of single-line rules for sets of _related_ rules, e.g.
+
+<!-- prettier-ignore -->
+```css
+/* Single-line related classes */
+.class-1 { top: 0; bottom: 0; }
+.class-2 { top: 5px; right: 0; }
+.class-3 { top: 8px; left: 0; }
+```
+
+You can configure the built-in stylistic rules to allow both multi-line and single-line rules. The choice of when to use each belongs to the user.
+
+## Validators
+
+Validators like [csstree](https://github.com/csstree/csstree) identify invalid code such as misformed hex colors and unknown language features.
+
+However, as a stop-gap, while these tools mature stylelint provides rules for the simplest of cases.

package/templates/facebook/node_modules/stylelint/docs/about/semantic-versioning.md

@@ -0,0 +1,37 @@
+# Semantic versioning
+
+Due to the nature of stylelint as a code quality tool, we follow a specific flavor of [semantic versioning](http://semver.org).
+
+Any minor update may report more errors than the previous release. As such, we recommend using the tilde (`~`) in `package.json` e.g. `"stylelint": "~7.2.0"` to guarantee the results of your builds.
+
+## Patch release
+
+Intended not to break your lint build:
+
+- a bug fix in a rule that results in stylelint reporting fewer errors
+- a bug fix to the CLI or core (including formatters)
+- improvements to documentation
+- non-user-facing changes such as refactoring code or modifying tests
+- re-releasing after a failed release (i.e., publishing a release that doesn't work for anyone)
+
+## Minor release
+
+Might break your lint build:
+
+- a bug fix in a rule that results in stylelint reporting more errors
+- a new rule is created
+- a new option to an existing rule that does not result in stylelint reporting more errors by default
+- an existing rule is deprecated
+- a new CLI capability is created
+- a new public API capability is created
+- a new formatter is created
+
+## Major release
+
+Likely to break your lint build:
+
+- a change in the documented behavior of an existing rule results in stylelint reporting more errors by default
+- an existing rule is removed
+- an existing formatter is removed
+- part of the CLI is removed or changed in an incompatible way
+- part of the public API is removed or changed in an incompatible way

package/templates/facebook/node_modules/stylelint/docs/about/syntaxes.md

@@ -0,0 +1,18 @@
+# Syntaxes
+
+There are many styling languages, ranging from CSS language extensions like SCSS to entirely different notations, e.g. CSS-in-JS objects.
+
+These styling languages can be embedded within other languages too. For example:
+
+- HTML `<style>` tags
+- markdown fences
+- JavaScript template literals
+
+We aim to support all these use cases in stylelint, but it's a complicated endeavor.
+
+We lean on [PostCSS syntaxes](https://github.com/postcss/postcss#syntaxes) to help us with this task. We use them to transform these languages into something that resembles CSS, which is the language that:
+
+- underpins all the other styling languages
+- is best understood by rules built into stylelint
+
+If you write your styles in anything other than CSS, please consider [contributing to these syntaxes](../developer-guide/syntaxes.md) so that they can remain compatible with stylelint.

package/templates/facebook/node_modules/stylelint/docs/about/vision.md

@@ -0,0 +1,63 @@
+# Vision
+
+A linter for CSS and CSS-like languages that is:
+
+- complete - coverage of all standard CSS syntax
+- extensible - multiple points of extension
+- configurable - no defaults and options to tailor the linter
+- robust - comprehensive test coverage and a wide range of fixtures
+- consistent - conventions for behavior, naming and documentation
+- performant - tools to test and improve performance
+
+## Complete
+
+Provide built-in rules for standard CSS syntax that:
+
+- [detect possible errors](../user-guide/rules/list.md#possible-errors)
+- [limit language features](../user-guide/rules/list.md#limit-language-features)
+- [enforce stylistic conventions](../user-guide/rules/list.md#stylistic-issues)
+
+### Possible errors
+
+Provide rules to catch code that is valid but likely has unintended consequences, e.g. duplicates and overrides.
+
+### Limit language features
+
+Provide rules to limit what language features can be used to enforce:
+
+- a maximum specificity by limiting the overall specificity or the occurrence of different selector types, e.g. class, ID and attribute
+- best practice _at the configuration level_, e.g. disallowing the `all` keyword for transitions
+- the use of a subset of features to improve consistency across a codebase, e.g. limiting what units are allowed
+- specific patterns for selectors and names, e.g. those of custom properties
+
+### Stylistic issues
+
+Provide rules to enforce a diverse range of stylistic conventions, including:
+
+- whitespace
+- case
+- quotes
+
+## Extensible
+
+Provide multiple points of extensions, including:
+
+- [plugins](../developer-guide/plugins.md) - build community rules to support methodologies, toolsets, non-standard CSS features, or very specific use cases
+- [extendable configs](../user-guide/configure.md#extends) - extend and share configurations
+- [formatters](../developer-guide/formatters.md) - format stylelint result objects
+- [custom syntax](syntaxes.md) - use any PostCSS-compatible syntax module
+
+## Robust
+
+Provide a robust tool with a [comprehensive test suite](../developer-guide/rules.md#write-tests), including:
+
+- high coverage, currently over 95%
+- a wide range of fixtures for rules
+
+## Consistent
+
+Provide consistency throughout, including consistent [rules](../user-guide/rules/about.md).
+
+## Performant
+
+Provide a fast tool and the means to test and improve performance, including [benchmarking](../developer-guide/rules.md#improve-the-performance-of-a-rule) of an individual rule's performance.

package/templates/facebook/node_modules/stylelint/docs/developer-guide/formatters.md

@@ -0,0 +1,77 @@
+# Writing formatters
+
+A formatter is a function with the following signature:
+
+```js
+/**
+ * @type {import('stylelint').Formatter}
+ */
+function formatter(results, returnValue) {
+  return "a string of formatted results";
+}
+```
+
+Where the first argument (`results`) is an array of stylelint result objects (type `Array<StylelintResult>`) in the form:
+
+```js
+// A stylelint result object
+{
+  "source": "path/to/file.css", // The filepath or PostCSS identifier like <input css 1>
+  "errored": true, // This is `true` if at least one rule with an "error"-level severity triggered a warning
+  "warnings": [
+    // Array of rule violation warning objects, each like the following ...
+    {
+      "line": 3,
+      "column": 12,
+      "rule": "block-no-empty",
+      "severity": "error",
+      "text": "You should not have an empty block (block-no-empty)"
+    }
+  ],
+  "deprecations": [
+    // Array of deprecation warning objects, each like the following ...
+    {
+      "text": "Feature X has been deprecated and will be removed in the next major version.",
+      "reference": "https://stylelint.io/docs/feature-x.md"
+    }
+  ],
+  "invalidOptionWarnings": [
+    // Array of invalid option warning objects, each like the following ...
+    {
+      "text": "Invalid option X for rule Y"
+    }
+  ],
+  "ignored": false // This is `true` if the file's path matches a provided ignore pattern
+}
+```
+
+And the second argument (`returnValue`) is an object (type `StylelintStandaloneReturnValue`) with one or more of the following keys:
+
+```js
+{
+  "errored": false, // `true` if there were any warnings with "error" severity
+  "maxWarningsExceeded": {
+    // Present if stylelint was configured with a `maxWarnings` count
+    "maxWarnings": 10,
+    "foundWarnings": 15
+  }
+}
+```
+
+## Passing arguments
+
+You can use environmental variables in your formatter. For example, pass `SKIP_WARNINGS`:
+
+```console
+SKIP_WARNINGS=true stylelint "*.css" --custom-formatter ./my-formatter.js
+```
+
+Alternatively, you can create a separate formatting program and pipe the output from the built-in JSON formatter into it:
+
+```console
+stylelint -f json "*.css" | my-program-that-reads-JSON --option
+```
+
+## `stylelint.formatters`
+
+stylelint's internal formatters are exposed publicly in `stylelint.formatters`.