himalaya

This minor release adds a new parse option includePositions. This is an opt-in feature that when set to true will cause himalaya.parse to emit nodes with a position field, containing start and end points. These points contain the zero-indexed index, line, and column numbers.

See this feature in the [README example](https://github.com/andrejewski/himalaya#line-column-and-index-position...

This release is a bug fix for issue #84 / PR #86.

There was a problem with unnecessary closing tags causing the parser to exit early, leaving later tags unparsed. For example, </i>x would return []. This is fixed, and tests added to prevent regression.

Thanks to @orballo for reporting this bug.

This major release includes a lot of changes (re-iterated from the PR):

• Dropping the Version 0 spec. In v0.2 Himalaya underwent huge internal changes in order to support multiple specification simultaneously with a shared parser powering these different formats. In v0.3 we introduced the v1 specification which co-existed alongside v0. Wh...

See #74 for the details.

Try this version with:

npm install himalaya@next

This patch release aligns Himalaya closer with the spec for HTML5 tag names in regards to valid tag names. Up until now, any characters following an < could be considered a tag name by the parser. Now that < must be immediately followed by an alphanumeric character.

Note: The HTML5 spec only allows purely alphanumeric tag names,...