saxes - npm Package Versions

4.0.0-rc.3 (2019-10-11)

Bug Fixes

• fix a bug in EOL handling (03b1567)
• implement attribute normalization (6580844), closes #24

Performance Improvements

• inline closeText (1c8df1a)

<a name="4.0.0-rc.2"></a>

4.0.0-rc.2 (2019-10-04)

Performance Improvements

• drop the originalNL flag in favor of a NL_LIKE fake character (f690725)
• dump isNaN; it is very costly (7d97e1a)
• eliminate extra buffers (3412fcb)
• reduce the number of calls to closeText (3e68df5)
• remove more extra buffers (b5ee774)
• use -1 to mean EOC (end-of-chunk) (55c0b1b)

<a name="4.0.0-rc.1"></a>

4.0.0-rc.1 (2019-10-02)

Bug Fixes

• don't serialize the fileName as undefined: when not present (4ff2365)
• fix bug with initial eol characters (7b3db75)
• handling of end of line characters (f13247a)

Features

• add forceXMLVersion (1eedbf8)
• saxes handles chunks that "break" unicode (1272448)
• support for XML 1.1 (36704fb)

Performance Improvements

• don't depend on limit to know when we hit the end of buffer (ad4ab53)
• don't increment a column number (490fc24)
• don't repeatedly read this.i in the getCode methods (d3f196c)
• improve performance of text handling (9c13099)
• make the most common path of getCode functions the shortest (4d66bbb)
• minimine concatenation by adding the capability to unget codes (27fa8b9)
• use isCharAndNotRestricted rather than call two functions (f0b67a4)
• use slice rather than substring (c1fed89)

BREAKING CHANGES

• previous versions of saxes did not consistently convert end of line characters to NL (0xA) in the data reported by event handlers. This has been fixed. If your code relied on the old (incorrect) behavior then you'll have to update it.
• previous versions of saxes would parse files with an XML declaration set to 1.1 as 1.0 documents. The support for 1.1 entails that if a document has an XML declaration that specifies version 1.1 it is parsed as a 1.1 document.
• when fileName is undefined in the parser options saxes does not show a file name in error messages. Previously it was showing the name undefined. To get the previous behavior, in all cases where you'd leave fileName undefined, you must set it to the string "undefined" instead.

<a name="3.1.11"></a>

3.1.11 (2019-06-25)

Bug Fixes

• pay attention to comments and processing instructions in DTDs (52ffd90), closes #19

Performance Improvements

• check the most common case first (40a34d5)
• improve some more the speed of ]]> detection (a0216cd)
• move more common/valid cases first (a65586e)
• split sText into two specialized loops (732325e)
• use specialized code for sAttribValueQuoted (6c484f3)

<a name="3.1.10"></a>

3.1.10 (2019-06-11)

Performance Improvements

• improve the check for ]]> in character data (21df9b5)

<a name="3.1.9"></a>

3.1.9 (2019-02-25)

Bug Fixes

• move eslint to devDependencies (d747538)

<a name="3.1.8"></a>

3.1.8 (2019-02-25)

<a name="3.1.7"></a>

3.1.7 (2019-02-22)

Bug Fixes

• npm audit warning (a6c9ba8)
• typings: "selfClosing" => "isSelfClosing" (d96a2bd)

<a name="3.1.6"></a>

3.1.6 (2019-01-17)

Bug Fixes

• detect unclosed tags in fragments (5642f36)

<a name="3.1.5"></a>

3.1.5 (2019-01-08)

Bug Fixes

• generate an error on prefix with empty local name (89a3b86), closes #5

<a name="3.1.4"></a>