karma-typescript-agile-preprocessor/CHANGELOG.md

Leverage the power of gulp-typescript for a simple yet powerful Karma preprocessor.

* 2.0.1:

  - Something changed between ``gulp-typescript`` 3.2.0 and 3.2.1 that causes
    this preprocessor to fail if used with ``gulp-typescript`` higher than
    3.2.0. As a stopgap measure, I'm pinning the maximum version of
    ``gulp-typescript`` to 3.2.0.

* 2.0.0:

  - Fork from ``karma-typescript-preprocessor2``.

  - The lowest supported version of Node is now 4.

  - The lowest supported version of ``gulp-typescript`` is now 3. The upside is
    that we no longer get a warning about a deprecated use of
    ``gulp-typescript``.

  - The plugin no longer explicitly requires ``typescript``, which means you can
    use it with any version of typescript that gulp-typescript supports.

    This was my main motivation for forking. I needed to use ``"extends"`` in
    ``tsconfig.json`` files. It worked everywhere except Karma. Yes, I did use
    my own ``typescript: require("typescript")`` in the ``karma.conf.js`` file
    to configure ``karma-typescript-preprocessor2``. **It still did not work.**
    I had to go delete the packages ``gulp-typescript`` and ``typescript`` that
    ``npm`` installed under ``karma-typescript-processor2/node_modules``, and I
    had to do this every time I installed or updated packages.

  - The code has been subjected to a general cleanup. It has been linted, many
    typos and inconsistencies have been fixed, bad practices have been
    eliminated. It is probably not perfect but much better than it was.

  - Reworked some of the internal logic. Hopefully, I've not broken anything.

  - When ``transformPath`` option is an array, it must contain only
    functions. Previous versions would ignore values that are not
    functions. Now it will cause a crash.

  - Dropped the usage of lodash/underscore.

    There was very little to be gained from using lodash/underscore in the
    plugin and in the test suite. The code of the plugin is meant to run in
    Node, and we've dropped support of anything prior to Node 4. So having a
    library handle edge cases on this and that browser is not useful.

    This change moreover eliminates a warning that lodash will no longer be
    accessible in Karma 2 and over.