1.2.0

• Implemented #3, the library now supports nested multi-line comments
• Fixed #4, errors are now reported correctly, with full details.

1.1.0

• Fixed bug #2
• Removed strict parsing for options, to be ignored when not an object.

1.0.0

• Removed support for Node.js 0.12.0, with Node.js 4.0.0 now being the new minimum.
• Converted all the code and tests to use ES6 syntax
• Updated DEV dependencies

v.0.5.5

• Dependency updates, now using strict ones only
• Retiring support for Node v0.10, adding support for Node v10

v.0.5.4

Dependency updates only.

v.0.5.3

Updating tests + documentation + dependencies.

No code changes.

v.0.5.2

New feature: preserving special multi-line comments

When a multi-line comment starts with /*!, it is no longer removed.

This is mostly for preparing SQL scripts where after compression you want to preserve a basic reference/name for it at the top, via a special-syntax multi-line comment that starts with /*!.

And the syntax of /*! comment */ is a known standard for comments that must not be removed.

Example:

/*! Special comment that won't be removed */
SELECT 123; -- this comment will be removed
/* This comment will also be removed */

v.0.5.1

Adding explicit verification and a new error code for nested multi-line comments.

Previously, nested multi-line comments were swallowed silently, generating an implicit incorrect result.

Now the library checks for nested multi-line comments, and if found - throws a new error:

SQLParsingError {
    code: parsingErrorCode.nestedMLC
    error: "Nested multi-line comments are not supported."
    position: {line: 2, col: 3}
}

v.0.5.0

This release was unpublished (replaced with 0.5.1), as it would report nested comments inside text blocks, which is incorrect.

v.0.4.5

• Refactoring much of the code and tests
• Documentation updates