7.0.0

[jlmakes]

The next major release of karma-rollup-preprocessor in response to Rollup 1.0 🎉

Pre-release

Added

• Support for Rollup 1.0.0 #42

Changed

• Breaking: Dropped support for Rollup < 1.0.0
• Breaking: Dropped support for Node < 8.0.0
• Watcher no longer relies on Karma’s run_start event. #41
• Upgraded dependencies.

Fixed

• Watcher only rebundles changed files and their dependents. #28
• Bundle cache now properly maps each entry to its bundle cache.

---

Hey all! 👋🏽

@isidrok @tatey @niksy @thisconnect @calebdwilliams @abaksha-sc @Paulskit @LvChengbin
@ckbo3hrk @pantosha @MartijnR @fengyuanchen @givanse @wifilinker @danielnaab

You all have participated in issues addressed in this release — if you don't mind, please help test by installing the pre-release (under the next tag):

npm install karma-rollup-preprocessor@next

[abaksha-sc]

Sorry, can't test it, because we use rollup 0.67.4 😢
​​​​​Could you release minor update for version 6.1 to fix issue #41?

[calebdwilliams]

@jlmakes I can confirm this works for my build. Thanks for all the hard work!

[fengyuanchen]

@jlmakes Got the following error with rollup@1.1.0:

ERROR [preprocessor.rollup]: Failed to process ./test\index.js

TypeError [ERR_INVALID_ARG_VALUE]: The argument 'path' must be a string or Uint8Array without null bytes. Received '\u0000commonjsHelpers'
    at Object.stat (fs.js:818:3)
    at FSWatcher.NodeFsHandler._addToNodeFs (~\node_modules\chokidar\lib\nodefs-handler.js:454:20)
    at FSWatcher.<anonymous> (~\node_modules\chokidar\index.js:648:12)
    at ~\node_modules\async-each\index.js:16:7
    at Array.forEach (<anonymous>)
    at each (~\node_modules\async-each\index.js:15:11)
    at FSWatcher.add (~\node_modules\chokidar\index.js:647:5)
    at Watcher.add (~\node_modules\karma-rollup-preprocessor\lib\Watcher.js:16:16)
    at preprocess (~\node_modules\karma-rollup-preprocessor\lib\index.js:24:15)

[jlmakes]

@fengyuanchen: Oooh, I forgot about null bytes! (re: #30)

@abaksha-sc: That seems like a reasonable request, although one thing that comes to mind is that the listening event was added in Karma 2 (breaking the watcher for anyone using Karma 1); karma was never an explicit peer dependency, but I'm still wondering if that would constitute a major release anyway.

Out of curiosity, why isn't your team upgrading to ^rollup@1 ?

[niksy]

@jlmakes works for my build!

[abaksha-sc]

Out of curiosity, why isn't your team upgrading to ^rollup@1 ?

Yes, we decided to try to upgrade ^rollup@1, but I just wanted to have "backup plan" if we will get some problems with upgrading. I thought that fix will be very simple (just replace event name), because I didn't know, that listening event was added in Karma 2 only. I hope rollup upgrading will be succedeed and minor release won't need.

[tatey]

@jlmakes Thanks for the update. I've tried this in my project and it's working great 👍

[fengyuanchen]

@jlmakes Works fine in my project now with karma-rollup-preprocessor@7.0.0-rc.2.

[LvChengbin]

It works for my build. @jlmakes Thank you for your project.

[givanse]

Works in my build, thanks:) 7.0.0-rc.2

    "rollup": "^1.1.0",
    "rollup-plugin-commonjs": "^9.2.0",
    "rollup-plugin-multi-entry": "^2.1.0",
    "rollup-plugin-node-resolve": "^4.0.0",
    "rollup-plugin-typescript": "^1.0.0",

[alexanderwende]

Thanks for your work, can confirm that 7.0.0-rc.2 works with

"karma": "^3.1.4",
"rollup": "^1.1.2",

[isidrok]

Works nice, thanks!

[jlmakes]

Thanks for the feedback everyone! 7.0.0 is live! 🎉