typed-typings / npm-first-mate

The type definition for https://github.com/atom/first-mate

Typed First Mate

The type definition for first-mate

LICENSE

MIT

Contributing

# Fork this repo
npm install

npm run watch

# add tests, make changes, pass tests ... then [ctrl+c]
npm run publish

Updating

Update typings.json/version to match the source version you are typing against. e.g. if you are creating typings for [email protected], then:

// typings.json
{
  "version": "3.5.0"
  // ...
}

npm-first-mate's Issues

An in-range update of tslint is breaking the build 🚨

Version 5.4.3 of tslint just got published.

Branch	Build failing 🚨
Dependency	tslint
Current Version	5.4.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As tslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v5.4.3

🛠 Bugfixes

• [bugfix] Fixed regression with empty --out file (#2867)
• [bugfix] unified-signatures: Don't suggest to unify rest parameters. (#2874)
• [bugfix] binary-expression-operand-order: Allow if both sides of the binary expression are literals. (#2873)
• [bugfix] Restore compatibility with [email protected] and 2.2 for whitespace, space-before-function-paren and deprecation (#2893)
• [docs] no-string-literal: Fix documentation (#2875)

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of ts-node is breaking the build 🚨

Version 3.0.5 of ts-node just got published.

Branch	Build failing 🚨
Dependency	ts-node
Current Version	3.0.4
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As ts-node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 7 commits.

• c18331a 3.0.5
• 5cf97b1 Add --inspect-brk to known flags (#343)
• 7dfb3e3 Pin node tests at 6.x (#340)
• 633d537 chore(package): update chai to version 4.0.1 (#337)
• b751a56 Define exports and improve getTypeInfo help (#332)
• d018300 Update yn default option
• cc3bf22 Expose _ bin file for consumers to use

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of onchange is breaking the build 🚨

Version 3.3.0 of onchange was just published.

Branch	Build failing 🚨
Dependency	onchange
Current Version	3.2.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

onchange is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

New `--filter` option

Added

• Pass --filter with a list of events to limit to

Commits

The new version differs by 4 commits.

• 92d2d33 3.3.0
• d4d090f Enable support for '--filter' (#55)
• fc1c092 Update dependencies to enable Greenkeeper 🌴 (#53)
• 6645eff fix: add .travis.yml

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of ts-node is breaking the build 🚨

Version 3.2.0 of ts-node just got published.

Branch	Build failing 🚨
Dependency	ts-node
Current Version	3.1.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As ts-node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

Boolean Env Flags

Changed

• Inherit boolean flags from environment
• Remove preferGlobal warning from package.json

Added

• Export printError utility
• Enable debug flag for hacking

Commits

The new version differs by 7 commits.

• d90ffba 3.2.0
• 2e03f54 fix(package): update chalk to version 2.0.0 (#372)
• c60d3a7 Export printError utility (#376)
• 3f0d975 Enable debug flag for method call tracking (#377)
• 394ddb8 Boolean flags inherit from env (#375)
• 82effb2 Handle possibly undefined diagnostic "start"
• 9bc3dd8 Remove preferGlobal from package.json

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴