Postcss Values Parser Versions Save

A CSS property value parser for PostCSS

v6.0.2

2 years ago

Bugfixes

  • fix: support parsing */ expressions without surrounding spaces (#144)
  • fix: Quoted – clone throw an error (#141) (#142 )

Updates

  • docs: fix numeric parse result (#139)

v6.0.0

2 years ago

Breaking Changes

  • feat!: update PostCSS, use NodeErrorOptions directly from PostCSS types (#133)

Bugfixes

  • fix: Function with dot inside name (#134)
  • fix: TypeScript types, add validation (#132)

v4.0.0

3 years ago

Updates

  • chore!: upgrade is-url-superb to ^4.0.0 (#125)

Breaking Changes

Node v10+ now required

v3.2.0

4 years ago

Bugfixes

fix: comma separated funcs with no spaces. fixes #91 fix: wonky function names. fixes #92 fix: numeric parsing (#109)

Features

feat: add hwb, lab, and lch to functions matching isColor (#111) …

Updates

test: add test for #104 test: add tests for #106

v3.0.5

4 years ago

Bugfixes

  • fix: add time value units (#87)

v3.0.4

5 years ago

Updates

  • Dependency updates and npm audit update

v3.0.3

5 years ago

Bugfixes

  • fix: quater milimeters not detected (#81)

Updates

  • docs: fix comment type (#78)

v3.0.2

5 years ago

Bugfixes

  • fix: toString should stringify node (#74)
  • fix: manipulation of node structures, proper stringifying (#73)

v3.0.0

5 years ago

Major Version 3

This is a major rewrite from top to bottom and contains many breaking changes. The rewrite leverages PostCSS itself under the hood. That means it uses the same tokenizer and parser, with some modifications. The last major update to PostCSS provided consumers with an outstanding model to inherit and extend from the base classes to create derived parsers. That means we now benefit from the rock-solid tokenizing in PostCSS without having to reinvent the wheel, and without introducing new bugs.

This also allows for use of the base PostCSS Node classes, without redefining or duplicating their functionality. Tasks like walking nodes, or inspecting Node properties you'd expect in PostCSS are now identical.

Breaking Changes

Some Node types have changed. Most notably, all characters which can be considered "punctuation" have been moved into the Punctuation Node. Additionally, decorative property names on Nodes have changed in some instances. The full API documentation has more details.

Old Node Type New Node Type
AtWord AtWord
Colon Punctuation
Comma Punctuation
Comment Comment
Func Func
Numbr Numeric
Operator Operator
Paren Punctuation
Str Quoted
UnicodeRange UnicodeRange
Word Word

v2.0.1

5 years ago

Bugfixes

  • fix: double slash comments inside Sass maps (#60)