No description
* optimize handling of RegEx parser results Previous: - Copy `results`, for every subsequent result of other `patterns` - Loop over results to filter out `undefined` values - Loop over results to map to `clipAtBalancedParens` Current: - For each candidate, push the `clipAtBalancedParens(candidate)` into the `results` This way we are not copying existing results, and we are also avoiding additional loops over the entire array to filter out `undefined` values and map to `clipAtBalancedParens`. * do not allow `]` in the first part of arbitrary properties ``` [foo:bar] ─┬─ └── This part cannot contain `]` ``` This is also a very targeted fix for when the arbitrary properties seem to match a large piece of text, but shouldn't * add real world tests for parsing candidate strings * sync package-lock.json * update changelog |
||
|---|---|---|
| .github | ||
| integrations | ||
| jest | ||
| nesting | ||
| oxide | ||
| perf | ||
| scripts | ||
| src | ||
| standalone-cli | ||
| stubs | ||
| tests | ||
| types | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.json | ||
| .gitignore | ||
| .swcrc | ||
| base.css | ||
| CHANGELOG.md | ||
| colors.d.ts | ||
| colors.js | ||
| components.css | ||
| defaultConfig.d.ts | ||
| defaultConfig.js | ||
| defaultTheme.d.ts | ||
| defaultTheme.js | ||
| LICENSE | ||
| loadConfig.d.ts | ||
| loadConfig.js | ||
| package-lock.json | ||
| package-lock.stable.json | ||
| package.json | ||
| package.stable.json | ||
| plugin.d.ts | ||
| plugin.js | ||
| prettier.config.js | ||
| README.md | ||
| resolveConfig.d.ts | ||
| resolveConfig.js | ||
| screens.css | ||
| tailwind.css | ||
| turbo.json | ||
| utilities.css | ||
| variants.css | ||
A utility-first CSS framework for rapidly building custom user interfaces.
Documentation
For full documentation, visit tailwindcss.com.
Community
For help, discussion about best practices, or any other conversation that would benefit from being searchable:
Discuss Tailwind CSS on GitHub
For casual chit-chat with others using the framework:
Join the Tailwind CSS Discord Server
Contributing
If you're interested in contributing to Tailwind CSS, please read our contributing docs before submitting a pull request.