v7.1.1

Compare Source

• perf: replace startsWith with strict equality (#​308)
• fix(types): add walkUniversal declaration (#​311)

v7.1.0

Compare Source

• feat: insert(Before|After) support multiple new node

v7.0.0

Compare Source

• Feat: make insertions during iteration safe (major)

v6.1.2

Compare Source

• Fixed: erroneous trailing combinators in pseudos

v6.1.1

Compare Source

• Fixed: improve typings of constructor helpers (#​292)

v6.1.0

Compare Source

• Feature: add sourceIndex to Selector nodes (#​290)

v6.0.16

Compare Source

• Fixed: add missing index argument to each/walk callback types (#​289)

v6.0.15

Compare Source

• Fixed: Node#prev and Node#next type for the first/last node

v6.0.14

Compare Source

• Fixed: type definitions

v6.0.13

Compare Source

• Fixed: throw on unexpected pipe symbols

v6.0.12

Compare Source

• Fixed: clone arguments should be optional

v6.0.11

Compare Source

• Fixed: parse attribute case insensitivity flag

v6.0.10

Compare Source

• Fixed: isPseudoElement() supports :first-letter and :first-line

v6.0.9

Compare Source

• Fixed: Combinator.raws property type

v6.0.8

Compare Source

• Fixed: reduced size

v6.0.7

Compare Source

• Fixed: parse animation percents

v6.0.6

Compare Source

• Fixed: parse quoted attributes containing a newline correctly

v6.0.5

Compare Source

• Perf: rework unesc for a 63+% performance boost

v6.0.4

Compare Source

• Fixed: ts errors

v6.0.3

Compare Source

• Fixed: replace node built-in "util" module with "util-deprecate"
• Fixed: handle uppercase pseudo elements
• Fixed: do not create invalid combinator before comment

v6.0.2

Compare Source

• Fixed an issue with parsing and stringifying an empty attribute value

v6.0.1

Compare Source

• Fixed: add missing index argument to each/walk callback types (#​289)

v6.0.0

Compare Source

• Updated: cssesc to 3.0.0 (major)
• Fixed: Issues with escaped id and class selectors

v5.0.0

Compare Source

• Allow escaped dot within class name.
• Update PostCSS to 7.0.7 (patch)

v4.0.0

Compare Source

This release has BREAKING CHANGES that were required to fix bugs regarding values with escape sequences. Please read carefully.

• Identifiers with escapes - CSS escape sequences are now hidden from the public API by default.
  The normal value of a node like a class name or ID, or an aspect of a node such as attribute
  selector's value, is unescaped. Escapes representing Non-ascii characters are unescaped into
  unicode characters. For example: bu\tton, .\31 00, #i\2764\FE0Fu, [attr="value is \"quoted\""]
  will parse respectively to the values button, 100, i❤️u, value is "quoted".
  The original escape sequences for these values can be found in the corresponding property name
  in node.raws. Where possible, deprecation warnings were added, but the nature
  of escape handling makes it impossible to detect what is escaped or not. Our expectation is
  that most users are neither expecting nor handling escape sequences in their use of this library,
  and so for them, this is a bug fix. Users who are taking care to handle escapes correctly can
  now update their code to remove the escape handling and let us do it for them.

• Mutating values with escapes - When you make an update to a node property that has escape handling
  The value is assumed to be unescaped, and any special characters are escaped automatically and
  the corresponding raws value is immediately updated. This can result in changes to the original
  escape format. Where the exact value of the escape sequence is important there are methods that
  allow both values to be set in conjunction. There are a number of new convenience methods for
  manipulating values that involve escapes, especially for attributes values where the quote mark
  is involved. See #​133 for an extensive
  write-up on these changes.

Upgrade/API Example

In 3.x there was no unescape handling and internal consistency of several properties was the caller's job to maintain. It was very easy for the developer
to create a CSS file that did not parse correctly when some types of values
were in use.

const selectorParser = require("postcss-selector-parser");
let attr = selectorParser.attribute({attribute: "id", operator: "=", value: "a-value"});
attr.value; // => "a-value"
attr.toString(); // => [id=a-value]
// Add quotes to an attribute's value.
// All these values have to be set by the caller to be consistent:
// no internal consistency is maintained.
attr.raws.unquoted = attr.value
attr.value = "'" + attr.value + "'";
attr.value; // => "'a-value'"
attr.quoted = true;
attr.toString();  // => "[id='a-value']"

In 4.0 there is a convenient API for setting and mutating values
that may need escaping. Especially for attributes.

const selectorParser = require("postcss-selector-parser");

// The constructor requires you specify the exact escape sequence
let className = selectorParser.className({value: "illegal class name", raws: {value: "illegal\\ class\\ name"}});
className.toString(); // => '.illegal\\ class\\ name'

// So it's better to set the value as a property
className = selectorParser.className();
// Most properties that deal with identifiers work like this
className.value = "escape for me";
className.value; // => 'escape for me'
className.toString(); // => '.escape\\ for\\ me'

// emoji and all non-ascii are escaped to ensure it works in every css file.
className.value = "😱🦄😍";
className.value; // => '😱🦄😍'
className.toString(); // => '.\\1F631\\1F984\\1F60D'

// you can control the escape sequence if you want, or do bad bad things
className.setPropertyAndEscape('value', 'xxxx', 'yyyy');
className.value; // => "xxxx"
className.toString(); // => ".yyyy"

// Pass a value directly through to the css output without escaping it. 
className.setPropertyWithoutEscape('value', '$REPLACE_ME$');
className.value; // => "$REPLACE_ME$"
className.toString(); // => ".$REPLACE_ME$"

// The biggest changes are to the Attribute class
// passing quoteMark explicitly is required to avoid a deprecation warning.
let attr = selectorParser.attribute({attribute: "id", operator: "=", value: "a-value", quoteMark: null});
attr.toString(); // => "[id=a-value]"
// Get the value with quotes on it and any necessary escapes.
// This is the same as reading attr.value in 3.x.
attr.getQuotedValue(); // => "a-value";
attr.quoteMark; // => null

// Add quotes to an attribute's value.
attr.quoteMark = "'"; // This is all that's required.
attr.toString(); // => "[id='a-value']"
attr.quoted; // => true
// The value is still the same, only the quotes have changed.
attr.value; // => a-value
attr.getQuotedValue(); // => "'a-value'";

// deprecated assignment, no warning because there's no escapes
attr.value = "new-value";
// no quote mark is needed so it is removed
attr.getQuotedValue(); // => "new-value";

// deprecated assignment, 
attr.value = "\"a 'single quoted' value\"";
// > (node:27859) DeprecationWarning: Assigning an attribute a value containing characters that might need to be escaped is deprecated. Call attribute.setValue() instead.
attr.getQuotedValue(); // => '"a \'single quoted\' value"';
// quote mark inferred from first and last characters.
attr.quoteMark; // => '"'

// setValue takes options to make manipulating the value simple.
attr.setValue('foo', {smart: true});
// foo doesn't require any escapes or quotes.
attr.toString(); // => '[id=foo]'
attr.quoteMark; // => null 

// An explicit quote mark can be specified
attr.setValue('foo', {quoteMark: '"'});
attr.toString(); // => '[id="foo"]'

// preserves quote mark by default
attr.setValue('bar');
attr.toString(); // => '[id="bar"]'
attr.quoteMark = null;
attr.toString(); // => '[id=bar]'

// with no arguments, it preserves quote mark even when it's not a great idea
attr.setValue('a value \n that should be quoted');
attr.toString(); // => '[id=a\\ value\\ \\A\\ that\\ should\\ be\\ quoted]'

// smart preservation with a specified default
attr.setValue('a value \n that should be quoted', {smart: true, preferCurrentQuoteMark: true, quoteMark: "'"});
// => "[id='a value \\A  that should be quoted']"
attr.quoteMark = '"';
// => '[id="a value \\A  that should be quoted"]'

// this keeps double quotes because it wants to quote the value and the existing value has double quotes.
attr.setValue('this should be quoted', {smart: true, preferCurrentQuoteMark: true, quoteMark: "'"});
// => '[id="this should be quoted"]'

// picks single quotes because the value has double quotes
attr.setValue('a "double quoted" value', {smart: true, preferCurrentQuoteMark: true, quoteMark: "'"});
// => "[id='a "double quoted" value']"

// setPropertyAndEscape lets you do anything you want. Even things that are a bad idea and illegal.
attr.setPropertyAndEscape('value', 'xxxx', 'the password is 42');
attr.value; // => "xxxx"
attr.toString(); // => "[id=the password is 42]"

// Pass a value directly through to the css output without escaping it. 
attr.setPropertyWithoutEscape('value', '$REPLACEMENT$');
attr.value; // => "$REPLACEMENT$"
attr.toString(); // => "[id=$REPLACEMENT$]"

v3.1.2

Compare Source

• Fix: Removed dot-prop dependency since it's no longer written in es5.

v3.1.1

Compare Source

• Fix: typescript definitions weren't in the published package.

v3.1.0

Compare Source

• Fixed numerous bugs in attribute nodes relating to the handling of comments
  and whitespace. There's significant changes to attrNode.spaces and attrNode.raws since the 3.0.0 release.
• Added Attribute#offsetOf(part) to get the offset location of
  attribute parts like "operator" and "value". This is most
  often added to Attribute#sourceIndex for error reporting.

v3.0.0

Compare Source

Breaking changes

• Some tweaks to the tokenizer/attribute selector parsing mean that whitespace
  locations might be slightly different to the 2.x code.
• Better attribute selector parsing with more validation; postcss-selector-parser
  no longer uses regular expressions to parse attribute selectors.
• Added an async API (thanks to @​jacobp100); the default process API is now
  async, and the sync API is now accessed through processSync instead.
• process() and processSync() now return a string instead of the Processor
  instance.
• Tweaks handling of Less interpolation (thanks to @​jwilsson).
• Removes support for Node 0.12.

Other changes

• ast() and astSync() methods have been added to the Processor. These
  return the Root node of the selectors after processing them.
• transform() and transformSync() methods have been added to the
  Processor. These return the value returned by the processor callback
  after processing the selectors.
• Set the parent when inserting a node (thanks to @​chriseppstein).
• Correctly adjust indices when using insertBefore/insertAfter (thanks to @​tivac).
• Fixes handling of namespaces with qualified tag selectors.
• process, ast and transform (and their sync variants) now accept a
  postcss rule node. When provided, better errors are generated and selector
  processing is automatically set back to the rule selector (unless the updateSelector option is set to false.)
• Now more memory efficient when tokenizing selectors.

Upgrade hints

The pattern of:

rule.selector = processor.process(rule.selector).result.toString();

is now:

processor.processSync(rule)