@biomejs/wasm-web

The README file is missing

Changelog

v1.8.3 (2024-06-27)

CLI

Bug fixes

• Fix #3104 by suppressing node warnings when using biome migrate. Contributed by @SuperchupuDev

• Force colors to be off when using the GitHub reporter to properly create annotations in GitHub actions (#3148). Contributed by @Sec-ant

Parser

Bug fixes

• Implement CSS unicode range. Contributed by @denbezrukov

Formatter

Bug fixes

• Fix #3184 CSS formatter converts custom identifiers to lowercase. Contributed by @denbezrukov
• Fix #3256 constant crashes when editing css files #3256. Contributed by @denbezrukov

Linter

New features

• Add nursery/useDeprecatedReason rule. Contributed by @vohoanglong0107.
• Add nursery/noExportedImports. Contributed by @Conaclos

Enhancements

• Implement suggestedExtensions option for useImportExtensions rule. Contributed by @drdaemos

Bug fixes

• useConsistentArrayType and useShorthandArrayType now ignore Array in the extends and implements clauses. Fix #3247. Contributed by @Conaclos
• Fixes #3066 by taking into account the dependencies declared in the package.json. Contributed by @ematipico
• The code action of the useArrowFunction rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #3292. Contributed by @Sec-ant

Enhancements

• Enhance tailwind sorting lint rule #1274 with variant support.

  Every preconfigured variant is assigned a weight that concurs on establishing the output sorting order. Since nesting variants on the same utility class is possible, the resulting weight is the Bitwise XOR of all the variants weight for that class. Dynamic variants (e.g. has-[.custom-class], group-[:checked]) are also supported and they take the weight of their base variant name the custom value attached (e.g. has-[.custom-class] takes has weight). Arbitrary variants (e.g. [&nth-child(2)]) don't have a weight assigned and they are placed after every known variant. Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last. Screen variants (e.g. sm:, max-md:, min-lg:) are not supported yet.

  Contributed by @lutaok