sessionStorage API which gracefully degrades to window.name & cookies when not available

Last update: Jul 25, 2022

Related tags

Overview

sessionstorage

The sessionStorage API is amazing and super useful when you need to store data temporarily in the browser. We used to abuse cookies for this, but not all the data that you want to store needs to be synced with the server. The sessionStorage API filled that gap, but unfortunately we cannot expect this API to be available and enabled in every browser context. This module provides various of fallbacks which follow the same API as sessionStorage for when it's not enabled. The following fallback's are supported:

window.name - Storing data in the name property of the window.
cookies - This doesn't really need an explanation.

Install

It's build for browserify but it should work with Node.js as well as we provide a fallback API. The module is released in the public npm registry and can be installed using:

npm install --save sessionstorage

Usage

The API is exactly the same as the DOM storage API so you can use the following methods:

getItem(key)
setItem(key, value)
removeItem(key)
clear()

So all you need to do is require the module and you're ready to go:

'use strict';

var sessionstorage = require('sessionstorage');

License

MIT

Comments

Update mocha to the latest version 🚀
Version 4.0.0 of mocha just got published.

Dependency mocha

Current Version 3.5.3

Type devDependency

The version 4.0.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of mocha. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Release Notes
v4.0.0
4.0.0 / 2017-10-02

You might want to read this before filing a new bug! 😝

💥 Breaking Changes

For more info, please read this article.

Compatibility

#3016: Drop support for unmaintained versions of Node.js (@boneskull):

0.10.x

0.11.x

0.12.x

iojs (any)

5.x.x

#2979: Drop support for non-ES5-compliant browsers (@boneskull):

IE7

IE8

PhantomJS 1.x

#2615: Drop Bower support; old versions (3.x, etc.) will remain available (@ScottFreeCode, @boneskull)

Default Behavior

#2879: By default, Mocha will no longer force the process to exit once all tests complete. This means any test code (or code under test) which would normally prevent node from exiting will do so when run in Mocha. Supply the --exit flag to revert to pre-v4.0.0 behavior (@ScottFreeCode, @boneskull)

Reporter Output

#2095: Remove stdout: prefix from browser reporter logs (@skeggse)

#2295: Add separator in "unified diff" output (@olsonpm)

#2686: Print failure message when --forbid-pending or --forbid-only is specified (@ScottFreeCode)

#2814: Indent contexts for better readability when reporting failures (@charlierudolph)

👎 Deprecations

#2493: The --compilers command-line option is now soft-deprecated and will emit a warning on STDERR. Read this for more info and workarounds (@ScottFreeCode, @boneskull)

🎉 Enhancements

#2628: Allow override of default test suite name in XUnit reporter (@ngeor)

📖 Documentation

#3020: Link to CLA in README.md and CONTRIBUTING.md (@skeggse)

🔩 Other

#2890: Speed up build by (re-)consolidating SauceLabs tests (@boneskull)

Commits

The new version differs by 48 commits.

d69bf14 Release v4.0.0

171b9f9 pfix "prepublishOnly" potential portability problem

60e39d9 Update link to wiki (GitHub at the leading --)

804f9d5 Update link because GitHub ate the leading --

3326c23 update CHANGELOG for v4.0.0 [ci skip]

6dd9252 add link to wiki on --compilers deprecation

96318e1 Deprecate --compilers

92beda9 drop bower support

58a4c6a remove unused .npmignore

7af6611 kill Date#toISOString shim

43501a2 reduce noise about slow tests; make a few tests faster, etc.

fa228e9 update --exit / --no-exit integration test for new default behavior

3fdd3ff Switch default from forced exit to no-exit

c5d69e0 add integration tests for --exit/--no-exit

3a7f8dc enhance runMochaJSON() helper by returning the subprocess instance

There are 48 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 :palm_tree:
greenkeeper
opened by greenkeeper[bot] 10
foo: bar is not removed (session storage test)
In index.js there is a test to write foo: bar to sessionStorage, and if it works it should be removed. However, foo: bar continues to exist in sessionStorage.

How to reproduce: Just import this package in a web project, build it and open it in a browser (I used chrome)

Observed behaviour: foo: bar exists in sessionStorage

Expected behaviour: foo: bar should be removed immediately after it's added

The code is very straight forward, so I can not understand how this bug can appear, but it does (and it does not appear when I don't include this package).
opened by arnemahl 7
sessionStorage and tape-tests
Dear developers,

I am using this library along with some unitests. Unfortunately it is not working correctly. This means, that I get an error that my sessionstorage is undefined.

Below I attach a sample of my code.

sessionStorage.setItem('auth', JSON.stringify(mockAuthData)); t.equal( sessionStorage.getItem('auth'), JSON.stringify(mockAuthData), 'must have saved the authentication token and user to session storage' );

This certainly should be true, since I explicitly set the sessionstorage. But it is not! Interestingly it works with localstorage.... Could you please consider correcting this bug or tell me what can I do in order to test stuff that uses sessionstorage

Greetings
opened by Irazall 4
Directly return the `sessionStorage` object when available

I think that when the sessionStorage object is available we can return it immediately without testing if it works properly, so we don't have to clean it up.

See #2.

opened by lpinca 2

Dependency	mocha
Current Version	3.5.3
Type	devDependency

Updating dependencies to fix high priority audit issues.

PR should address npm audit findings:

npm audit --prod

                       === npm audit security report ===

┌──────────────────────────────────────────────────────────────────────────────┐
│                                Manual Review                                 │
│            Some vulnerabilities require your attention to resolve            │
│                                                                              │
│         Visit https://go.npm.me/audit-guide for additional guidance          │
└──────────────────────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High          │ Prototype Override                                           │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ querystringify                                               │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in    │ ≥ 2.0.0                                                      │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ window.name                                                  │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ window.name > querystringify                                 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/1634,- [WhiteSource             │
│               │ Advisory](https://www.whitesourcesoftware.com/vulnerability… │
│               │ - [Snyk                                                      │
│               │ Advisory](https://snyk.io/vuln/npm:querystringify:20180419)  │
│               │ - [GitHub                                                    │
│               │ Advisory](https://github.com/advisories/GHSA-hxcm-v35h-mg2x) │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High          │ Prototype Override                                           │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ querystringify                                               │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in    │ ≥ 2.0.0                                                      │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ koekje                                                       │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ koekje > querystringify                                      │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/1634,- [WhiteSource             │
│               │ Advisory](https://www.whitesourcesoftware.com/vulnerability… │
│               │ - [Snyk                                                      │
│               │ Advisory](https://snyk.io/vuln/npm:querystringify:20180419)  │
│               │ - [GitHub                                                    │
│               │ Advisory](https://github.com/advisories/GHSA-hxcm-v35h-mg2x) │
└───────────────┴──────────────────────────────────────────────────────────────┘
found 2 high severity vulnerabilities in 12 scanned packages
  2 vulnerabilities require manual review. See the full report for details.

opened by pwilder-sig 1

Update assume to the latest version 🚀

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.0.0 of assume was just published.

Dependency assume

Current Version 1.5.2

Type devDependency

The version 2.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 assume.

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.

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 :palm_tree:
greenkeeper

opened by greenkeeper[bot] 1
Update mocha to the latest version 🚀
Version 3.4.0 of mocha just got published.

Dependency mocha

Current Version 3.3.0

Type devDependency

The version 3.4.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of mocha. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

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 :palm_tree:
greenkeeper
opened by greenkeeper[bot] 1
Update mocha to the latest version 🚀
Version 3.5.0 of mocha just got published.

Dependency mocha

Current Version 3.4.2

Type devDependency

The version 3.5.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of mocha. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Release Notes
free-as-in-freezing
3.5.0 / 2017-07-31

📰 News

Mocha now has a code of conduct (thanks @kungapal!).

Old issues and PRs are now being marked "stale" by Probot's "Stale" plugin. If an issue is marked as such, and you would like to see it remain open, simply add a new comment to the ticket or PR.

WARNING: Support for non-ES5-compliant environments will be dropped starting with version 4.0.0 of Mocha!

🔒 Security Fixes

#2860: Address CVE-2015-8315 via upgrade of debug (@boneskull)

🎉 Enhancements

#2696: Add --forbid-only and --forbid-pending flags. Use these in CI or hooks to ensure tests aren't accidentally being skipped! (@charlierudolph)

#2813: Support Node.js 8's --napi-modules flag (@jupp0r)

🔩 Other

Various CI-and-test-related fixes and improvements (@boneskull, @dasilvacontin, @PopradiArpad, @Munter, @ScottFreeCode)

"Officially" support Node.js 8 (@elergy)

Commits

The new version differs by 34 commits.

82d879f Release v3.5.0

bf687ce update mocha.js for v3.5.0

ec73c9a update date for release of v3.5.0 in CHANGELOG [ci skip]

1ba2cfc update CHANGELOG.md for v3.5.0 [ci skip]

065e14e remove custom install script from travis (no longer needed)

4e87046 update karma-sauce-launcher URL for npm@5

6886ccc increase timeout for slow-grepping test

2408d90 Make dependencies use older version of readable-stream to work around incompatibilities introduced by 2.3.0 on June 19th

68a1466 Try not clearing the env for debug in the integration test and see if that fixes Node 0.10 on AppVeyor; if need be, some other fix/workaround can be applied to handle whatever was up with debug without causing this issue

958fbb4 Update new tests to work in browser per test hierarchy reorganization

1df7c94 Merge pull request #2704 from seppevs/increase_test_coverage_of_mocha_js

1f270cd Stop timing out (#2889)

27c7496 upgrade to [email protected]; closes #2859 (#2860)

50fc47d fix CI; closes #2867 (#2868)

1b1377c Add test for ignoreLeaks and fix descriptions

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 :palm_tree:
greenkeeper
opened by greenkeeper[bot] 0
Update koekje to the latest version 🚀
Version 0.1.0 of koekje just got published.

Dependency koekje

Current Version 0.0.4

Type dependency

The version 0.1.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of koekje. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Commits

The new version differs by 6 commits.

93c61cc Merge branch 'master' of github.com:unshiftio/koekje

486f9f5 [dist] 0.1.0

e916d95 [fix] Use koekiemonster

f2b9fe7 [ignore] Add .npmignore

aeb3590 [travis] Clean up .travis.yml

4fe0d01 [deps] Bump devDependencies

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 :palm_tree:
greenkeeper
opened by greenkeeper[bot] 0
Update mocha to the latest version 🚀
Version 3.3.0 of mocha just got published.

Dependency mocha

Current Version 3.2.0

Type devDependency

The version 3.3.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of mocha. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Release Notes
coverave
Thanks to all our contributors, maintainers, sponsors, and users! ❤️

As highlights:

We've got coverage now!

Testing is looking less flaky \o/.

No more nitpicking about "mocha.js" build on PRs.

🎉 Enhancements

#2659: Adds support for loading reporter from an absolute or relative path (@sul4bh)

#2769: Support --inspect-brk on command-line (@igwejk)

🐛 Fixes

#2662: Replace unicode chars w/ hex codes in HTML reporter (@rotemdan)

🔍 Coverage

#2672: Add coverage for node tests (@c089, @Munter)

#2680: Increase tests coverage for base reporter (@epallerols)

#2690: Increase tests coverage for doc reporter (@craigtaub)

#2701: Increase tests coverage for landing, min, tap and list reporters (@craigtaub)

#2691: Increase tests coverage for spec + dot reporters (@craigtaub)

#2698: Increase tests coverage for xunit reporter (@craigtaub)

#2699: Increase tests coverage for json-stream, markdown and progress reporters (@craigtaub)

#2703: Cover .some() function in utils.js with tests (@seppevs)

#2773: Add tests for loading reporters w/ relative/absolute paths (@sul4bh)

🔩 Other

Remove bin/.eslintrc; ensure execs are linted (@boneskull)

#2542: Expand CONTRIBUTING.md (@boneskull)

#2660: Double timeouts on integration tests (@Munter)

#2653: Update copyright year ([@Scottkao85], @Munter)

#2621: Update dependencies to enable Greenkeeper (@boneskull, @greenkeeper)

#2625: Use trusty container in travis-ci; use "artifacts" addon (@boneskull)

#2670: doc(CONTRIBUTING): fix link to org members (@coderbyheart)

Add Mocha propaganda to README.md (@boneskull)

#2470: Avoid test flake in "delay" test (@boneskull)

#2675: Limit browser concurrency on sauce (@boneskull)

#2669: Use temporary test-only build of mocha.js for browsers tests (@Munter)

Fix "projects" link in README.md (@boneskull)

#2678: Chore(Saucelabs): test on IE9, IE10 and IE11 (@coderbyheart)

#2648: Use semistandard directly (@kt3k)

#2727: Make the build reproducible (@lamby)

Commits

The new version differs by 89 commits0.

fb1687e :ship: Release v3.3.0

1943e02 Add Changelog for v3.3.0

861e968 Refactor literal play-icon hex code to a var

1d3c5bc Fix typo in karma.conf.js

9bd9389 Fix spec paths in test HTML files

0a93024 Adds tests for loading reporters w/ relative/absolute paths (#2773)

73929ad Comment special treatment of '+' in URL query parsing

e2c9514 Merge pull request #2769 from igwejk/support_inspect_break_in_opts

038c636 Support --inspect-brk on command-line

b4ebabd Merge pull request #2727 from lamby/reproducible-build

882347b Please make the build reproducible.

a2fc76c Merge pull request #2703 from seppevs/cover_utils_some_fn_with_tests

ed61cd0 cover .some() function in utils.js with tests

f42cbf4 Merge pull request #2701 from craigtaub/landingSpec

6065242 use stubbed symbol

There are 89 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 :palm_tree:
greenkeeper
opened by greenkeeper[bot] 0
Update assume to the latest version 🚀
Version 1.5.0 of assume just got published.

Dependency assume

Current Version 1.4.1

Type devDependency

The version 1.5.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of assume. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Commits

The new version differs by 8 commits .

181f634 [dist] 1.5.0

7efc4be Merge pull request #21 from decompil3d/eitherOfType

cfa5f10 Merge branch 'eitherOfType' of github.com:decompil3d/assume into eitherOfType

b0ba0e0 [fix] Get rid of 'some' version of fix

9e077d3 [tiny][doc] Fix typo in README.md

f636767 [fix][test] Support older browsers that lack Array.prototype.some

b8c68dc Derp. Fix readme example for eitherOf

15d5d7d [api] Add eitherOfType/oneOfType assertion

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 :palm_tree:
greenkeeper
opened by greenkeeper[bot] 0
Bug with node session

Currently these session-variables get lost, whenever a file or the folder structure is changed. In my current project, changing the folder structure (e.g. adding new files) is a functionality and every time this function gets called or i save a file, the user gets logged out, due to the session being killed for no reason.

As this package is the only simple and clean solution to node sessions, I've found, this is very unfortunate.

opened by KoenigAlfonz 0
querystringify vulnerability

Hey there, snyk is reporting a vulnerability. Any chance of this being fixed or being looked into?

Introduced through: [email protected] › [email protected] › [email protected] Introduced through: [email protected] › [email protected] › [email protected]

https://app.snyk.io/vuln/npm:querystringify:20180419

opened by Brianzchen 0
Update koekje to the latest version 🚀

The dependency koekje was updated from 0.1.0 to 0.2.0.

This version 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.

Publisher: 3rdeden License: MIT

Find out more about this release.

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 :palm_tree:
greenkeeper

opened by greenkeeper[bot] 0
Update window.name to the latest version 🚀

The dependency window.name was updated from 0.0.3 to 0.0.4.

This version 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.

Publisher: 3rdeden License: MIT

Find out more about this release.

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 :palm_tree:
greenkeeper

opened by greenkeeper[bot] 0
Update mocha to the latest version 🚀
The devDependency mocha was updated from 5.2.0 to 6.0.0.

This version 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.

Release Notes for v6.0.0

6.0.0 / 2019-02-18

💥 Breaking Changes

#3149: Drop Node.js v4.x support (@outsideris)

#3556: Changes to command-line options (@boneskull):

--grep and --fgrep are now mutually exclusive; attempting to use both will cause Mocha to fail instead of simply ignoring --grep

--compilers is no longer supported; attempting to use will cause Mocha to fail with a link to more information

-d is no longer an alias for --debug; -d is currently ignored

#3275: --watch-extensions no longer implies js; it must be explicitly added (@TheDancingCode)

#2908: tap reporter emits error messages (@chrmod)

#2819: When conditionally skipping in a before hook, subsequent before hooks and tests in nested suites are now skipped (@bannmoore)

#627: Emit filepath in "timeout exceeded" exceptions where applicable (@boneskull)

#3556: lib/template.html has moved to lib/browser/template.html (@boneskull)

#2576: An exception is now thrown if Mocha fails to parse or find a mocha.opts at a user-specified path (@plroebuck)

#3458: Instantiating a Base-extending reporter without a Runner parameter will throw an exception (@craigtaub)

#3125: For consumers of Mocha's programmatic API, all exceptions thrown from Mocha now have a code property (and some will have additional metadata). Some Error messages have changed. Please use the code property to check Error types instead of the message property; these descriptions will be localized in the future. (@craigtaub)

📠 Deprecations

These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:

-gc users should use --gc-global instead

Consumers of the function exported by bin/options should now use the loadMochaOpts or loadOptions (preferred) functions exported by the lib/cli/options module

Regarding the Mocha class constructor (from lib/mocha):

Use property color: false instead of useColors: false

Use property timeout: false instead of enableTimeouts: false

All of the above deprecations were introduced by #3556.

mocha.opts is now considered "legacy"; please prefer RC file or package.json over mocha.opts.

🎉 Enhancements

#3726: Add ability to unload files from require cache (@plroebuck)

Enhancements introduced in #3556:

Mocha now supports "RC" files in JS, JSON, YAML, or package.json-based (using mocha property) format

.mocharc.js, .mocharc.json, .mocharc.yaml or .mocharc.yml are valid "rc" file names and will be automatically loaded

Use --config /path/to/rc/file to specify an explicit path

Use --package /path/to/package.json to specify an explicit package.json to read the mocha prop from

Use --no-config or --no-package to completely disable loading of configuration via RC file and package.json, respectively

Configurations are merged as applicable using the priority list:

Command-line arguments

RC file

package.json

mocha.opts

Mocha's own defaults

Check out these example config files

Node/V8 flag support in mocha executable:

Support all allowed node flags as supported by the running version of node (also thanks to @demurgos)

Support any V8 flag by prepending --v8- to the flag name

All flags are also supported via config files, package.json properties, or mocha.opts

Debug-related flags (e.g., --inspect) now imply --no-timeouts

Use of e.g., --debug will automatically invoke --inspect if supported by running version of node

Support negation of any Mocha-specific command-line flag by prepending --no- to the flag name

Interfaces now have descriptions when listed using --interfaces flag

Mocha constructor supports all options

--extension is now an alias for --watch-extensions and affects non-watch-mode test runs as well. For example, to run only test/*.coffee (not test/*.js), you can do mocha --require coffee-script/register --extensions coffee.

#3552: tap reporter is now TAP13-capable (@plroebuck & @mollstam)

#3535: Mocha's version can now be queried programmatically via public property Mocha.prototype.version (@plroebuck)

#3428: xunit reporter shows diffs (@mlucool)

#2529: Runner now emits a retry event when tests are retried (reporters can listen for this) (@catdad)

#2962, #3111: In-browser notification support; warn about missing prereqs when --growl supplied (@plroebuck)

🐛 Fixes

#3737: Fix falsy values from options globals (@plroebuck)

#3707: Fix encapsulation issues for Suite#_onlyTests and Suite#_onlySuites (@vkarpov15)

#3711: Fix diagnostic messages dealing with plurality and markup of output (@plroebuck)

#3723: Fix "reporter-option" to allow comma-separated options (@boneskull)

#3722: Fix code quality and performance of lookupFiles and files (@plroebuck)

#3650, #3654: Fix noisy error message when no files found (@craigtaub)

#3632: Tests having an empty title are no longer confused with the "root" suite (@juergba)

#3666: Fix missing error codes (@vkarpov15)

#3684: Fix exiting problem in Node.js v11.7.0+ (@addaleax)

#3691: Fix --delay (and other boolean options) not working in all cases (@boneskull)

#3692: Fix invalid command-line argument usage not causing actual errors (@boneskull)

#3698, #3699: Fix debug-related Node.js options not working in all cases (@boneskull)

#3700: Growl notifications now show the correct number of tests run (@outsideris)

#3686: Avoid potential ReDoS when diffing large objects (@cyjake)

#3715: Fix incorrect order of emitted events when used programmatically (@boneskull)

#3706: Fix regression wherein --reporter-option/--reporter-options did not support comma-separated key/value pairs (@boneskull)

Fix missing mocharc.json in published package (@boneskull)

#3356: --no-timeouts and --timeout 0 now does what you'd expect (@boneskull)

#3475: Restore --no-exit option (@boneskull)

#3570: Long-running tests now respect SIGINT (@boneskull)

#2944: --forbid-only and --forbid-pending now "fail fast" when encountered on a suite (@outsideris)

#1652, #2951: Fix broken clamping of timeout values (@plroebuck)

#2753: start and end events now emitted properly from Runner instance when using Mocha programmatically (@outsideris)

#2095, #3521: Do not log stdout: prefix in browser console (@Bamieh)

#3595: Fix mochajs.org deployment problems (@papandreou)

#3518: Improve utils.isPromise() (@fabiosantoscode)

#3320: Fail gracefully when non-extensible objects are thrown in async tests (@fargies)

#2475: XUnit does not duplicate test result numbers in "errors" and "failures"; "failures" will always be zero (@mlucool)

#3398, #3598, #3457, #3617: Fix regression wherein --bail would not execute "after" nor "after each" hooks (@juergba)

#3580: Fix potential exception when using XUnit reporter programmatically (@Lana-Light)

#1304: Do not output color to TERM=dumb (@plroebuck)

📖 Documentation

#3525: Improvements to .github/CONTRIBUTING.md (@markowsiak)

#3466: Update description of slow option (@finfin)

#3405: Remove references to bower installations (@goteamtim)

#3361: Improvements to --watch docs (@benglass)

#3136: Improve docs around globbing and shell expansion (@akrawchyk)

#2819: Update docs around skips and hooks (@bannmoore)

Many improvements by @outsideris

#3652: Switch from Jekyll to Eleventy (@Munter)

🔩 Other

#3677: Add error objects for createUnsupportedError and createInvalidExceptionError (@boneskull)

#3733: Removed unnecessary processing in post-processing hook (@wanseob)

#3730: Update nyc to latest version (@coreyfarrell)

#3648, #3680: Fixes to support latest versions of unexpected and unexpected-sinon (@sunesimonsen)

#3638: Add meta tag to site (@MartijnCuppens)

#3653: Fix parts of test suite failing to run on Windows (@boneskull)

#3557: Use ms userland module instead of hand-rolled solution (@gizemkeser)

Many CI fixes and other refactors by @plroebuck

Test refactors by @outsideris

Commits

The new version differs by 209 commits ahead by 209, behind by 39.

42303e2 Release v6.0.0

a553ca7 punctuation updates for changelog v6.0.0

c710792 grammar updates for changelog v6.0.0

9f9293a update changelog for v6.0.0

a540eb0 remove "projects" section from MAINTAINERS.md [ci skip]

52b5c42 Uppercased JSON reporter name in describe title (#3739)

82307fb Fix .globals to remove falsy values (#3737)

56dc28e Remove unnecessary post-processing code having no effect; closes #3708 (#3733)

16b4281 Documentation updates (#3728)

5d9d3eb Update nyc

118c9ae Refactor out usages of Suite#_onlyTests and Suite#_onlyTests (#3689) (#3707)

0dacd1f Add ability to unload files from require cache (redux) (#3726)

66a52f2 update release steps [ci skip]

45ae014 Refactor lookupFiles and files (#3722)

94c9320 fix --reporter-option to allow comma-separated options; closes #3706

There are 209 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 :palm_tree:
greenkeeper
opened by greenkeeper[bot] 15
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

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 :robot:

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 :palm_tree:
greenkeeper
opened by greenkeeper[bot] 0