An in-range update of css-loader is breaking the build 🚨

Version 0.28.3 of css-loader just got published.

Branch	Build failing 🚨
Dependency	css-loader
Current Version	0.28.2
Type	dependency

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

css-loader is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

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 eslint-plugin-import is breaking the build 🚨

Version 2.8.0 of eslint-plugin-import was just published.

Branch	Build failing 🚨
Dependency	eslint-plugin-import
Current Version	2.7.0
Type	devDependency

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

eslint-plugin-import 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/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 35 commits.

95b1ba6 disable AppVeyor coveralls
4071379 #842/#944 changelog note
8702af7 #744 changelog note
91c5318 #886 / #891 changelog notes
1b3f544 bump v2.8.0
cef88f2 Merge pull request #944 from alexgorbatchev/alexgorbatchev/issue-842
c246b9e #842 Fixes Cannot read property 'some' of undefined
1958e0b [Tests] fix broken test on master
68f63f5 forgot @k15a's user link 😅
5f5fbf6 changelog notes for #620 + #632
92dd662 Merge pull request #632 from k15a/master
1ba1c3a removing changelog note, will re-add
146f87f changelog notes for #720 + #858
57527c7 Merge pull request #858 from laysent/master
006ddeb Merge remote-tracking branch 'refs/remotes/benmosher/master'

There are 35 commits in total.

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 postcss-loader is breaking the build 🚨

Version 2.0.7 of postcss-loader was just published.

Branch	Build failing 🚨
Dependency	postcss-loader
Current Version	2.0.6
Type	dependency

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

postcss-loader is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v2.0.7

2017-10-10

Bug Fixes

sanitizing from and to options (postcss.config.js) (#260) (753dea7)
index: runaway promise (#269) (8df20ce)

Commits

The new version differs by 14 commits.

30d8d51 chore(release): 2.0.7
e066f34 test: refactor (#299)
aaf1672 chore(package): update jest v20.0.0...21.0.0
305840c chore(.github): add PULL_REQUEST_TEMPLATE
cd7cc1f chore(.github): add ISSUE_TEMPLATE
0ec251d chore(.github): add CODEOWNERS for review
081a638 docs(README): add loader description (#298)
813bcbd docs(README): readd ident: postcss to examples (options.ident) (#297)
8df20ce fix(index): runaway promise (#269)
44f01bb docs(README): remove autoprefixer from example (#289)
403f5e2 fix(index): runaway promise (#269)
f512a20 docs(README): add missing comma in example (#295)
271ab9a chore(package): update webpack v2.6.1...3.0.0 (devDependencies) (#270)
753dea7 fix: sanitizing from and to options (postcss.config.js) (#260)

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 🌴

resolve extra paths (like .shared) for the backend build

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

Version 1.5.0 of resolve was just published.

Branch	Build failing 🚨
Dependency	resolve
Current Version	1.4.0
Type	dependency

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

resolve is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 10 commits.

19cbd5e v1.5.0
e0c5d51 [Tests] on node v8.8
7f509ba [New] node v8.8+ supports http2
b826f30 [Fix] fix broken core tests; change core.json to be an object instead of an array; fix results
e66117d [New] add perf_hooks, added in node v8.5
d0de222 [Tests] up to node 8.7; use nvm install-latest-npm so new npm doesn’t break old node
5bfb072 [Dev Deps] update eslint
e9d3a24 [Tests] up to v8.4; node 0.6 is failing due to travis-ci changes; allow it to fail for now.
76f28a3 [Dev Deps] update eslint, @ljharb/eslint-config, tape
3412f98 [Docs] update repo URL

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 nock is breaking the build 🚨

Version 9.4.1 of nock was just published.

Branch	Build failing 🚨
Dependency	nock
Current Version	9.4.0
Type	devDependency

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

nock 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/appveyor/branch AppVeyor build failed Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v9.4.1

9.4.1 (2018-07-02)

Bug Fixes

request overrider checks req.headers to parse body as JSON (#1157) (f81fb6d)

Commits

The new version differs by 2 commits.

5aa1081 docs: Add CONTRIBUTE, edit README, update LICENSE year (#1155)
f81fb6d fix: request overrider checks req.headers to parse body as JSON (#1157)

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 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml
The engines config in 1 of your package.json files was too ambiguous to be updated automatically

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

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 sinon is breaking the build 🚨

Version 2.3.0 of sinon just got published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	2.2.0
Type	devDependency

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

As sinon 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 is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

Feature: stub accessors in sandbox

Allow stubbing of accessors with and without sandbox (#1416)
add throwsArg(index) to stubs (#1319)
Fix: forEach() requires 'this' argument (#1356)
Only reset history when calling resetHistory()

Commits

The new version differs by 34 commits.

64d51be Update docs/changelog.md and set new release id in docs/_config.yml
d4b30b0 Add release documentation for v2.3.0
8d64248 2.3.0
e137139 Update Changelog.txt and AUTHORS for new release
55dc491 Merge pull request #1416 from lucasfcosta/refactor-sandbox-stub
fb514cf Merge pull request #1415 from mroderick/style-improvements
06bf652 Merge pull request #1414 from mroderick/add-related-libraries-to-how-to-page
746de3f Force fenced code blocks to use smaller font
1602e00 Improve styling of h4
46fd81b Remove deprecation warning from tests for old API
454e0fd Add missing final dot to sandbox docs
0ea3e17 Add docs for stub.value
c89fb21 Deprecate stubbing sandbox value in favor of value behavior
dbefd45 Name restore function on stubNonFunctionProperty
fe3b9ac Add related libraries section to How To page

There are 34 commits in total.

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 babel-preset-env is breaking the build 🚨

Version 1.5.1 of babel-preset-env just got published.

Branch	Build failing 🚨
Dependency	babel-preset-env
Current Version	1.5.0
Type	dependency

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

babel-preset-env is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v1.5.1

v1.5.1 (2017-05-22)

🐛 Bug Fix

Compile with loose mode (#322) (@existentialism)

Commits

The new version differs by 3 commits.

5ff37e3 1.5.1
86ce2db Update changelog for v1.5.1 [skip ci]
cb11cb1 Compile with loose mode (#332)

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 mocha is breaking the build 🚨

Version 3.4.0 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.3.0
Type	dependency

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

mocha is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

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

Release Notes

v3.4.0

Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.

This week's highlights:

allowUncaught added to commandline as --allow-uncaught (and bugfixed)
warning-related Node flags

🎉 Enhancements

#2793, #2697: add --allowUncaught to Node.js (@lrowe)
#2733: Add --no-warnings and --trace-warnings flags (@sonicdoe)

🐛 Fixes

#2793, #2697: fix broken allowUncaught (@lrowe)

🔩 Other

#2778: Add license report and scan status (@xizhao)
#2794: no special case for macOS running Karma locally (@boneskull)
#2795: reverts use of semistandard directly ([#2648]) (@boneskull)

Commits

The new version differs by 9 commits0.

7554b31 Add Changelog for v3.4.0
9f7f7ed Add --trace-warnings flag
92561c8 Add --no-warnings flag
ceee976 lint test/integration/fixtures/simple-reporter.js
dcfc094 Revert "use semistandard directly"
93392dd no special case for macOS running Karma locally
4d1d91d --allow-uncaught cli option
fb1e083 fix allowUncaught in browser
4ed3fc5 Add license report and scan status

false

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 coveralls is breaking the build 🚨

Version 2.13.2 of coveralls just got published.

Branch	Build failing 🚨
Dependency	coveralls
Current Version	2.13.1
Type	devDependency

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

As coveralls 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 is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 3 commits.

5ebe57f bump version
428780c Expand allowed dependency versions to all API compatible versions (#172)
eb1b723 Update Mocha link (#169)

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 eslint-plugin-import is breaking the build 🚨

Version 2.9.0 of eslint-plugin-import was just published.

Branch	Build failing 🚨
Dependency	eslint-plugin-import
Current Version	2.8.0
Type	devDependency

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

eslint-plugin-import 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/appveyor/branch AppVeyor build failed Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 101 commits.

180d71a bump plugin to v2.9.0
0231c78 Merge pull request #1026 from isiahmeadows/patch-1
ae5a031 Missed a link
5b0777d Add no-default-export + docs/tests (#936)
ff3d883 Merge pull request #1025 from patrick-steele-idem/update-dependencies
654d284 Merge pull request #1024 from patrick-steele-idem/issue-1023
9b20a78 Upgraded "find-root" and "lodash.get" for the webpack resolver
8778d7c Fixes #1023 - Load exceptions in user resolvers are not reported
91cfd6d Merge pull request #1022 from nevir/patch-1
0e729c7 no-self-import is unreleased
219a8d2 Merge pull request #1012 from silvenon/extensions-export
ab49972 Support export declarations in extensions rule
3268a82 Merge pull request #1010 from silvenon/extensions
fdcd4d9 Add a .coffee test proving extension resolve order
bc50394 Merge pull request #1009 from silvenon/extensions

There are 101 commits in total.

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 nyc is breaking the build 🚨

Version 11.3.0 of nyc was just published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	11.2.1
Type	devDependency

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

nyc 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 is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 12 commits.

d85118c chore(release): 11.3.0
7792733 chore: explicitly update istanbul dependencies (#698)
222a3d0 chore: slight difference in pinning logic, based on @ljharb's advice
f04b7a9 feat: add option to hook vm.runInContext (#680)
cdfdff3 feat: add --exclude-after-remap option for users who pre-instrument their codebase (#697)
a413f6a chore: upgrade to yargs 10 (#694)
10125aa docs: fix reporters link
f5089ca docs: added examples of coverage reports (#656)
af281e7 chore: update spawn-wrap to 1.4.0 (#692)
a685f7c docs: missing options prefix -- in front of check-coverage (#695)
f31d7a6 feat: allow instrument-only to produce sourcemaps (#674)
425c0fd chore: ignore package-lock.json (#683)

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 node-sass is breaking the build 🚨

Version 4.6.0 of node-sass was just published.

Branch	Build failing 🚨
Dependency	node-sass
Current Version	4.5.3
Type	dependency

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

node-sass is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v4.6.0

Fixes

Node 9 Support
Some Electron ABIs allowed
Watcher improvements

Supported Environments

OS	Architecture	Node
Windows	x86 & x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9
OSX	x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9
Linux*	x86 & x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9
Alpine	x64	4, 6, 7, 8
FreeBSD 10+	i386	4, 6, 8
FreeBSD 10+	amd64	4, 6, 8

*Linux support refers to Ubuntu, Debian, and CentOS 5

Commits

The new version differs by 27 commits.

54f9873 4.6.0
0e8ce9c Build: Add Node 9 to Appveyor
82dc901 Install: Add Node 9 detection
8110422 build: Add Node 8 (carbon) to Travis
74242dc Merge pull request #2127 from foladipo/patch-1
aa5bbbf improve grammar/clarity of instructions
e934a55 Remove Node 0.10 and 0.12 from CI config (#2112)
6ed334b Add workaround for Node < 4 support with v4.x
9e18803 docs: Fix broken anchor for Functions
4a0f3d0 docs: README formatting and spelling fixes (#2063)
5392533 chore: add NPM 5 troubleshooting (#2036)
a219c8c Fix broken link to CONTRIBUTING.md
4f9b667 docs: Replace VS 2013 requirement with node-gyp (#2028)
74179fc Fix test exclusion
59fb078 Pass "follow" option to sass-graph

There are 27 commits in total.

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 postcss-loader is breaking the build 🚨

Version 2.0.9 of postcss-loader was just published.

Branch	Build failing 🚨
Dependency	postcss-loader
Current Version	2.0.8
Type	dependency

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

postcss-loader is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v2.0.9

2017-11-24

`Bug Fixes`

index: filter ident (options.ident) (#315) (3e1c7fa)

Commits

The new version differs by 4 commits.

b9c1add chore(release): 2.0.9
3e1c7fa fix(index): filter ident (options.ident) (#315)
f33131c test: filter ident (options.ident) (#314)
31a25e8 docs(README): fix broken link (importLoaders) (#310)

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 sinon is breaking the build 🚨

Version 2.3.5 of sinon just got published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	2.3.4
Type	devDependency

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

As sinon 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 is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

Fix: Check configurable on a prop before creating

Check configurable on a prop before creating (fixes #1456) (#1462)

Commits

The new version differs by 8 commits.

33f32ac Update docs/changelog.md and set new release id in docs/_config.yml
d00ab2b Add release documentation for v2.3.5
1c690aa 2.3.5
cc0a3fb Update Changelog.txt and AUTHORS for new release
ef2ecec Check configurable on a prop before creating (fixes #1456) (#1462)
e7dbfd7 Merge pull request #1460 from gj/patch-1
512018f Fix minor typos
d60d4a2 Fix apostrophe typos (#1454)

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 sinon is breaking the build 🚨

Version 2.3.2 of sinon just got published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	2.3.1
Type	devDependency

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

As sinon 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 is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

Minor fixes

Fix failing sandbox.resetBehavior() (#1428)
Fix restoring getters/setters/values for previously unexisting props (#1419)
Called in order takes callCount into account. Closes #1398.

Commits

The new version differs by 17 commits.

2463d10 Update docs/changelog.md and set new release id in docs/_config.yml
2e6bb45 Add release documentation for v2.3.2
87abc01 2.3.2
96e8abe Update Changelog.txt and AUTHORS for new release
2f941e2 Merge pull request #1406 from lucasfcosta/called-in-order-considers-callcount
3af985a Merge pull request #1427 from fearphage/remove-try-from-tests
c81d76b Merge pull request #1428 from fatso83/failing-sandbox-reset
0bf0a79 Fix failing sandbox.resetBehavior()
be4e53b Add failing tests for sandbox.reset()
fe049aa Add code snippet for createStubInstance (#1423)
9e23c4a added rule to prevent try-catch usage in tests
528a7dc switched from try-catch to assert.exception()
d8dac84 Add downloads per month banner to README.md
e933add Add site/_docs/ to .eslintignore
ebe37da Add documentation for "has" matcher on embedded objects (#1422)

There are 17 commits in total.

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 nock is breaking the build 🚨

Version 9.0.15 of nock just got published.

Branch	Build failing 🚨
Dependency	nock
Current Version	9.0.14
Type	devDependency

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

As nock 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 is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 4 commits.

029be32 9.0.15
a82d4d4 fix: nock.define() respects badheaders option
9aa493a test: nock.define() ignores badheaders option
1433789 docs(README): document nock.recorder.clear()

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 sinon is breaking the build 🚨

Version 4.0.2 of sinon was just published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	4.0.1
Type	devDependency

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

sinon 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/appveyor/branch AppVeyor build failed Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 21 commits.

39e5737 Update docs/changelog.md and set new release id in docs/_config.yml
c2bd7b1 Add release documentation for v4.0.2
da24e94 4.0.2
cea60e8 Update History.md and AUTHORS for new release
d4dcfca Document the stub.reset breaking change (#1590)
aab1917 Merge pull request #1596 from mroderick/fix-preversion-to-use-history.md
5dbe685 Update 'nise' to latest version (#1593)
578b9ea Update History.md and AUTHORS for new release
499b698 Fix preversion.sh to stage History.md
1e5fd0f Remove unneeded characters
2a69d51 fix typo in contributing
6cc71ec Document how to trigger progress events (#1585)
e49fcf1 Fix broken test-coverage task
527086a Use supports-color module to test if system supports colors
78782b4 Merge pull request #1580 from mroderick/dependency-hygeine

There are 21 commits in total.

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 mocha is breaking the build 🚨

Version 3.5.2 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.5.1
Type	devDependency

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

As mocha 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/appveyor/branch AppVeyor build failed Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details
✅ greenkeeper/verify Greenkeeper verified pull request Details
✅ security/snyk No new issues Details
❌ continuous-integration/appveyor/pr AppVeyor build failed Details
❌ continuous-integration/travis-ci/pr The Travis CI build failed Details

Release Notes

v3.5.2

3.5.2 / 2017-09-10

🐛 Fixes

#3001: Fix AMD-related failures first appearing in v3.5.1 (@boneskull)

Commits

The new version differs by 5 commits.

72622ab Release v3.5.2
ac4c39f fix version in CHANGELOG.md [ci skip]
f06d969 update CHANGELOG for 3.5.2 [ci skip]
9a3ddeb fix AMD bundle by hacking around check in he module; closes #3000
337d317 fix broken links in CHANGELOG.md [ci skip]

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 nock is breaking the build 🚨

Version 9.0.25 of nock was just published.

Branch	Build failing 🚨
Dependency	nock
Current Version	9.0.24
Type	devDependency

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

nock 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 is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v9.0.25

9.0.25 (2017-10-23)

Bug Fixes

re-add support for matching body to query string regex (#1006) (be7a075)

Commits

The new version differs by 2 commits.

be7a075 fix: re-add support for matching body to query string regex (#1006)
f22dcc3 docs(readme): Documentation Update for activate, isActive, restore methods. (#1002)

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 webpack is breaking the build 🚨

Version 2.6.0 of webpack just got published.

Branch	Build failing 🚨
Dependency	webpack
Current Version	2.5.1
Type	dependency

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

webpack is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 24 commits.

859b8cd updated examples
af05c14 2.6.0
74afac5 Merge pull request #4881 from webpack/bugfix/destructing
cd6d086 fix missing pattern walk
231a638 fix parsing issue with patterns
272c105 support destructing on assignment
6bd3a82 Merge pull request #4902 from bdwain/master
04f2622 require a newer version of uglify that fixes a bug with regexp
6d24f0d Merge pull request #4882 from kdnk/fix-typo
7e4d659 CI
60f154f archieved —> achieved
95400b8 Merge pull request #4865 from PeterTeng/peter/fix-typo-in-examples
d5d0428 Merge pull request #4880 from webpack/ci/appveyor-yarn
8ee65f1 Workaround for weird yarn link behavior
b59e179 'it it' => 'in in'

There are 24 commits in total.

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 supertest is breaking the build 🚨

Version 3.1.0 of supertest was just published.

Branch	Build failing 🚨
Dependency	`supertest`
Current Version	3.0.0
Type	devDependency

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

supertest 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/appveyor/branch AppVeyor build failed Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v3.1.0

#473 - Remove unused dependency in Readme (thanks @pedro-otero)
#472 - Update travis node versions (thanks @rimiti)
#470 - Upgrade the superagent node module to resolve security vulnerabilities & fix the proto property deprecation (thanks @levioza)
#446 - Fix bug, always pass on errors if no response (thanks @bkeepers)
#418 - Add post() examples to the README (thanks @kevinburke)
#297 - Add a .host() method to set a host other than 127.0.0.1 (thanks @mikec)
#275 - Removed ambiguously misappropriated cultural references from readme (thanks @reallistic)

Commits

The new version differs by 1 commits.

d4a63af Release v3.1.0 (#474)

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 webpack is breaking the build 🚨

Version 2.6.1 of webpack just got published.

Branch	Build failing 🚨
Dependency	webpack
Current Version	2.6.0
Type	dependency

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

webpack is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v2.6.1

Bugfixes:

Promise is now only needed when loading chunk, not in initialization
variable injection in require.ensure is now working again
better comment message when no export found (output.pathinfo)

Commits

The new version differs by 7 commits.

7cfd2c4 2.6.1
5ec15f8 Merge pull request #4927 from webpack/bugfix/require-ensure-var-inject
da08b89 fix variable injection in require.ensure
0dd0830 Merge pull request #4923 from webpack/bugfix/promise-later
09d9533 Use Promise only when chunk load is triggered
ae389b0 Merge pull request #4918 from marzelin/master
08615a2 change description when no static exports found

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 sinon is breaking the build 🚨

Version 2.3.3 of sinon just got published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	2.3.2
Type	devDependency

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

As sinon 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 is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

Make stubbing of static function properties possible

Fix #1450, make stubbing of static function properties possible

Commits

The new version differs by 24 commits.

bade318 Update docs/changelog.md and set new release id in docs/_config.yml
65d4e88 Add release documentation for v2.3.3
2204e72 2.3.3
64034ee Update Changelog.txt and AUTHORS for new release
1ece07c Merge pull request #1450 from raulmatei/fix-1445-sandbox-stubbing-static-function-property-throws-error
452981c Fix 1445: make stubbing of static function properties possible
25f3eeb Update sandbox configuration docs. (#1443)
c76fa2e Merge pull request #1444 from piperchester/patch-1
6539d94 Update README.md
c6d01d8 Add missing function name (#1440)
5f989a8 Remove confusing .withArgs from spy documentation (#1438)
9ca272e Remove superfluous calls in example (#1437)
9e3eac3 Merge pull request #1436 from sinonjs/feature-detect-name-property
65d3d7b Feature detect function name property in issue 950
e0c75bd Add test for #950, show that it has been fixed (#1435)

There are 24 commits in total.

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 sinon is breaking the build 🚨

Version 2.3.4 of sinon just got published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	2.3.3
Type	devDependency

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

As sinon 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 is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details
❌ coverage/coveralls Coverage pending from Coveralls.io Details

Release Notes

Make sandbox.resetHistory also reset spies

Fix #1372: make sandbox.resetHistory also reset spies (#1424)

Commits

The new version differs by 5 commits.

72ae300 Update docs/changelog.md and set new release id in docs/_config.yml
769d770 Add release documentation for v2.3.4
c8d2ec0 2.3.4
d27976a Update Changelog.txt and AUTHORS for new release
330101a Fix #1372: make sandbox.resetHistory also reset spies (#1424)

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 extract-text-webpack-plugin is breaking the build 🚨

Version 3.0.1 of extract-text-webpack-plugin just got published.

Branch	Build failing 🚨
Dependency	extract-text-webpack-plugin
Current Version	3.0.0
Type	dependency

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

extract-text-webpack-plugin is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch AppVeyor build failed Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

Release v3.0.1

3.0.1 (2017-10-03)

Bug Fixes

index: stricter check for shouldExtract !== wasExtracted (#605) (510704f)
get real path from __filename instead of __dirname (NS) (8de6558)

Commits

The new version differs by 5 commits.

4cfde50 chore(release): 3.0.1
8de6558 fix: get real path from __filename instead of __dirname (NS)
510704f fix(index): stricter check for shouldExtract !== wasExtracted (#605)
6a660f3 docs(README): update install instructions (#570)
083a6c8 docs(README): add custom [contenthash] formats (#566)

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 🌴

Hot reload does not work with .md files?

getting started docs wip

Installation

install aden via

npm i aden -g

Getting started

make an example folder
navigate to it
type:

touch .server
echo "Hello World" > index.html
aden -d

Open your web browser at localhost:5000 => Hello World!

Aden just set up an express server and configured it to deliver the index.html file located in your root directory. now you can add index.html oder index.js files to subdirectorys of your root folder, without worrying about setting up routes or delivering payload.

Aden will do that for you.

mkdir sub
cd sub
echo "This is another route aden just created for me"  > index.html

localhost:5000/sub

What exactly did i just do?

The .server file designates it's folder to be the root of the server filesystem. it can contain configuration options or middlewares. aden parses all subdirecorys contained by the root for index files and sets up routes corresponding to the filesystem.

$ aden runs aden. without a specified path, she uses your working directory as root folder (should contain the .server file).

The -d flag puts aden in devmode. in devmode aden features hot module reload, watches your filesystem for changes and generates new routes as you change files and directorys.

TL;DR

npm i aden -g => touch .server => aden -d => use filesystem like a webserver of the days of olde.

Features

Aden conveniently wraps the wall of configuration for webpack and the ever repeating route/controller setup for express, removing a lot of cognitive overhead.

Devmode `-d`

Watches filesystem for changes and sets up routes life for faster iteration. implements webpacks hot module reload.

Build `-b`

Builds your frontend for production via webpack (including babel transpiling, minification and uglification) and the corresponding backend for node.js and express.

Supported filetypes

Aden can handle .html, .js, .css, and .hbs files for now. support is modular an can be turned off for less overhead.

An in-range update of eslint-plugin-import is breaking the build 🚨

Version 2.4.0 of eslint-plugin-import just got published.

Branch	Build failing 🚨
Dependency	eslint-plugin-import
Current Version	2.3.0
Type	devDependency

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

As eslint-plugin-import 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 is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 10 commits.

44ca158 update utils changelog
a3728d7 bump eslint-module-utils to v2.1.0
3e29169 bump v2.4.0
ea9c92c Merge pull request #737 from kevin940726/master
8f9b403 fix typos, enforce type of array of strings in allow option
95315e0 update CHANGELOG.md
28e1623 eslint-module-utils: filePath in parserOptions (#840)
2f690b4 update CI to build on Node 6+7 (#846)
7d41745 write doc, add two more tests
dedfb11 add allow glob for rule no-unassigned-import, fix #671

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 🌴

Vendor Attitude https://github.com/kommander/aden/pull/83

See #83

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

Version 0.6.1 of brokens just got published.

Branch	Build failing 🚨
Dependency	brokens
Current Version	0.6.0
Type	dependency

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

brokens is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 4 commits.

0722713 Version 0.6.1
602d6f1 satisfy linter
cc11128 Use correct error name in message and stack
f4beecc rename

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 morgan is breaking the build 🚨

Version 1.8.2 of morgan just got published.

Branch	Build failing 🚨
Dependency	morgan
Current Version	1.8.1
Type	dependency

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

morgan is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

1.8.2

deps: [email protected]
- Fix DEBUG_MAX_ARRAY_LENGTH
- deps: [email protected]

Commits

The new version differs by 12 commits.

475ae38 1.8.2
b33ed70 deps: [email protected]
864a036 build: [email protected]
ab10b6c build: [email protected]
714577d build: [email protected]
fb33e99 tests: add stream option tests
d265d9f build: [email protected]
e17e76f build: [email protected]
3be5721 build: test against Node.js 8.x nightly
30d7053 build: [email protected]
23b6a30 build: [email protected]
8074ed6 build: [email protected]

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 eslint-plugin-import is breaking the build 🚨

Version 2.3.0 of eslint-plugin-import just got published.

Branch	Build failing 🚨
Dependency	eslint-plugin-import
Current Version	2.2.0
Type	devDependency

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

As eslint-plugin-import 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/appveyor/branch AppVeyor build failed Details
❌ coverage/coveralls Coverage pending from Coveralls.io Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details

Commits

The new version differs by 46 commits.

b79e083 Merge pull request #837 from benmosher/release-2.3.0
74425a2 changelog update for 2.3.0
1377f55 bump v2.3.0
2efc41a fix null pointer exception (#717) (#797)
0fb592e Add support to specify the package.json (#685)
2cc9768 Add test for flow type export (#835)
bd0e5e3 Merge pull request #821 from smably/patch-1
412e518 Clarify docs for glob arrays
106740f chore(package): update typescript-eslint-parser to version 2.1.0 (#790)
6288cf9 chore(package): update babel-register to version 6.24.1 (#796)
2e9eea6 newline-after-import test syntax fails
c9f10e8 extensions test fixes, attempt 2
861765f fix babel syntax errors in extensions tests
82f796c chore(package): update cross-env to version 4.0.0 (#783)
98e7048 Merge pull request #757 from gmathieu/fix-default-keyword

There are 46 commits in total.

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 extract-text-webpack-plugin is breaking the build 🚨

Version 3.0.2 of extract-text-webpack-plugin was just published.

Branch	Build failing 🚨
Dependency	extract-text-webpack-plugin
Current Version	3.0.1
Type	dependency

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

extract-text-webpack-plugin is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/appveyor/branch AppVeyor build failed Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

Release v3.0.2

3.0.2 (2017-10-25)

Bug Fixes

refer to the entrypoint instead of the first module (module.identifier) (#601) (d5a1de2)

Commits

The new version differs by 3 commits.

cc3ba94 chore(release): 3.0.2
d5a1de2 fix: refer to the entrypoint instead of the first module (module.identifier) (#601)
5286ab2 build(defaults): update to v1.6.0 (#652)

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 mocha is breaking the build 🚨

Version 3.4.2 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.4.1
Type	dependency

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

mocha is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch AppVeyor build failed Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/mocha-3.4.2 at 86.482% Details

Release Notes

fake-success

3.4.2 / 2017-05-24

🐛 Fixes

#2802: Remove call to deprecated os.tmpDir (@makepanic)
#2820: Eagerly set process.exitCode (@chrisleck)

🔩 Other

#2778: Move linting into an npm script (@Munter)

Commits

The new version differs by 7 commits.

a15b20a :ship: Release v3.4.2
fc802a9 :memo: Add Changelog for v3.4.2
10ff0ec Eagerly set process.exitCode (#2820)
fc35691 Merge pull request #2818 from makepanic/issue/2802
3e7152f Remove call to deprecated os.tmpDir (#2802)
e249434 Merge pull request #2807 from mochajs/npm-script-lint
17a1770 Move linting into an npm script. Relates to #2805

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 🌴

kommander / aden Goto Github PK

aden's People

Contributors

Stargazers

Watchers

Forkers

aden's Issues

Version 0.28.3 of css-loader just got published.

Version 2.8.0 of eslint-plugin-import was just published.

Version 2.0.7 of postcss-loader was just published.

Bug Fixes

Version 1.5.0 of resolve was just published.

Version 9.4.1 of nock was just published.

9.4.1 (2018-07-02)

Bug Fixes

Version 10 of Node.js (code name Dubnium) has been released! 🎊

Version 2.3.0 of sinon just got published.

Version 1.5.1 of babel-preset-env just got published.

v1.5.1 (2017-05-22)

🐛 Bug Fix

Version 3.4.0 of mocha just got published.

🎉 Enhancements

🐛 Fixes

🔩 Other

Version 2.13.2 of coveralls just got published.

Version 2.9.0 of eslint-plugin-import was just published.

Version 11.3.0 of nyc was just published.

Version 4.6.0 of node-sass was just published.

Fixes

Supported Environments

Version 2.0.9 of postcss-loader was just published.

Bug Fixes

Version 2.3.5 of sinon just got published.

Version 2.3.2 of sinon just got published.

Version 9.0.15 of nock just got published.

Version 4.0.2 of sinon was just published.

Version 3.5.2 of mocha just got published.

3.5.2 / 2017-09-10

🐛 Fixes

Version 9.0.25 of nock was just published.

9.0.25 (2017-10-23)

Bug Fixes

Version 2.6.0 of webpack just got published.

Version 3.1.0 of supertest was just published.

Version 2.6.1 of webpack just got published.

Bugfixes:

Version 2.3.3 of sinon just got published.

Version 2.3.4 of sinon just got published.

Version 3.0.1 of extract-text-webpack-plugin just got published.

3.0.1 (2017-10-03)

Bug Fixes

Installation

Getting started

What exactly did i just do?

TL;DR

Features

Devmode -d

Build -b

Supported filetypes

Version 2.4.0 of eslint-plugin-import just got published.

Version 0.6.1 of brokens just got published.

Version 1.8.2 of morgan just got published.

Version 2.3.0 of eslint-plugin-import just got published.

Version 3.0.2 of extract-text-webpack-plugin was just published.

3.0.2 (2017-10-25)

Bug Fixes

Version 3.4.2 of mocha just got published.

3.4.2 / 2017-05-24

🐛 Fixes

🔩 Other

Recommend Projects

Recommend Topics

Recommend Org

`Bug Fixes`

Devmode `-d`

Build `-b`