The version 9.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of espower-typescript.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesv9.0.0
Breaking changes
Drop Node v4 and add v10
Drop TypeScript v2.2 and v2.3
Require installing typescript in your project local now
Use ts-node instead of typescript-simple internally
Type checking is enabled by default now
It requires npm i -D @types/node @types/mocha additionally
To disable type checking, use TS_NODE_TRANSPILE_ONLY=1 env for ts-node
Some other changes from typescript-simple
Features
allowJs: true in tsconfig.json enables to instrument .js files (#51)
Bugfixes
Some issues are fixed by replacing to ts-node
Commits
The new version differs by 12 commits ahead by 12, behind by 2.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 9.0.0 of espower-typescript was just published.
[espower-typescript](https://github.com/power-assert-js/espower-typescript)The version 9.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of espower-typescript.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v9.0.0Breaking changes
typescriptin your project local nownpm i -D @types/node @types/mochaadditionallyTS_NODE_TRANSPILE_ONLY=1env for ts-nodeFeatures
allowJs: trueintsconfig.jsonenables to instrument.jsfiles (#51)Bugfixes
Commits
The new version differs by 12 commits ahead by 12, behind by 2.
d4761759.0.02389ca9build: remove publishConfig from package.json14b863adocs: update reamde0bd9c5dMerge pull request #52 from power-assert-js/next14b839fdocs: improve readme063720e9.0.0-beta.0a9ea286build: add package.json > publishConfig > tag: nextf497868docs: update README0d9edf5Merge pull request #51 from power-assert-js/allowjs2b0ededfix: update for latest codebasedcfa445feat: transpile.jsfiles as well ifallowJs:trueexists in tsconfig.json5a44611Use ts-node instead of typescript-simple (#50)See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: