Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): update devdependencies (non-major) (major) #41

Merged
merged 1 commit into from
Feb 3, 2022
Merged

chore(deps): update devdependencies (non-major) (major) #41

merged 1 commit into from
Feb 3, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 3, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/mocha 7.0.2 -> 9.1.0 age adoption passing confidence
@types/node 14.18.10 -> 16.11.22 age adoption passing confidence
ansi-regex >=5.0.1 -> 6.0.1 age adoption passing confidence
mocha (source) 7.2.0 -> 9.2.0 age adoption passing confidence
sinon (source) 8.1.1 -> 13.0.1 age adoption passing confidence
ts-node (source) 8.10.2 -> 10.4.0 age adoption passing confidence
typescript (source) 3.9.10 -> 4.5.5 age adoption passing confidence

Release Notes

chalk/ansi-regex

v6.0.1

Compare Source

Fixes
  • Fix ReDoS in certain cases (#​37)
    You are only really affected if you run the regex on untrusted user input in a server context, which it's very unlikely anyone is doing, since this regex is mainly used in command-line tools.

CVE-2021-3807

Thank you @​yetingli for the patch and reproduction case!

v6.0.0

Compare Source

Breaking

v5.0.1

Compare Source

Fixes (backport of 6.0.1 to v5)

This is a backport of the minor ReDos vulnerability in ansi-regex@<6.0.1, as requested in #​38.

  • Fix ReDoS in certain cases (#​37)
    You are only really affected if you run the regex on untrusted user input in a server context, which it's very unlikely anyone is doing, since this regex is mainly used in command-line tools.

CVE-2021-3807

Thank you @​yetingli for the patch and reproduction case!

v5.0.0

Compare Source

Breaking
Enhancements

v4.1.0

Compare Source

v4.0.0

Compare Source

mochajs/mocha

v9.2.0

Compare Source

🎉 Enhancements

🔩 Other

v9.1.4

Compare Source

🐛 Fixes

🔩 Other

v9.1.3

Compare Source

🐛 Fixes

🔩 Other

v9.1.2

Compare Source

🐛 Fixes

🔩 Other

v9.1.1

Compare Source

🐛 Fixes

v9.1.0

Compare Source

🎉 Enhancements

v9.0.3

Compare Source

🐛 Fixes

v9.0.2

Compare Source

🐛 Fixes

🔩 Other

v9.0.1

Compare Source

🔩 Other

We added a separate browser bundle mocha-es2018.js in javascript ES2018, as we skipped the transpilation down to ES5. This is an experimental step towards freezing Mocha's support of IE11.

v9.0.0

Compare Source

💥 Breaking Changes

Mocha is going ESM-first! This means that it will now use ESM import(test_file) to load the test files, instead of the CommonJS require(test_file). This is not a problem, as import can also load most files that require does. In the rare cases where this fails, it will fallback to require(...). This ESM-first approach is the next step in Mocha's ESM migration, and allows ESM loaders to load and transform the test file.

🎉 Enhancements

🐛 Fixes

🔩 Other

v8.4.0

Compare Source

🎉 Enhancements

🐛 Fixes

📖 Documentation

Also thanks to @​outsideris for various improvements on our GH actions workflows.

v8.3.2

Compare Source

🐛 Fixes

📖 Documentation

v8.3.1

Compare Source

🐛 Fixes

v8.3.0

Compare Source

🎉 Enhancements

🐛 Fixes

📖 Documentation

🔩 Other

Also thanks to @​outsideris and @​HyunSangHan for various fixes to our website and documentation.

v8.2.1

Compare Source

Fixed stuff.

🐛 Fixes

  • #​4489: Fix problematic handling of otherwise-unhandled Promise rejections and erroneous "done() called twice" errors (@​boneskull)
  • #​4496: Avoid MaxListenersExceededWarning in watch mode (@​boneskull)

Also thanks to @​akeating for a documentation fix!

v8.2.0

Compare Source

The major feature added in v8.2.0 is addition of support for global fixtures.

While Mocha has always had the ability to run setup and teardown via a hook (e.g., a before() at the top level of a test file) when running tests in serial, Mocha v8.0.0 added support for parallel runs. Parallel runs are incompatible with this strategy; e.g., a top-level before() would only run for the file in which it was defined.

With global fixtures, Mocha can now perform user-defined setup and teardown regardless of mode, and these fixtures are guaranteed to run once and only once. This holds for parallel mode, serial mode, and even "watch" mode (the teardown will run once you hit Ctrl-C, just before Mocha finally exits). Tasks such as starting and stopping servers are well-suited to global fixtures, but not sharing resources--global fixtures do not share context with your test files (but they do share context with each other).

Here's a short example of usage:

// fixtures.js

// can be async or not
exports.mochaGlobalSetup = async function() {
  this.server = await startSomeServer({port: process.env.TEST_PORT});
  console.log(`server running on port ${this.server.port}`);
};

exports.mochaGlobalTeardown = async function() {
  // the context (`this`) is shared, but not with the test files
  await this.server.stop();
  console.log(`server on port ${this.server.port} stopped`);
};

// this file can contain root hook plugins as well!
// exports.mochaHooks = { ... }

Fixtures are loaded with --require, e.g., mocha --require fixtures.js.

For detailed information, please see the documentation and this handy-dandy flowchart to help understand the differences between hooks, root hook plugins, and global fixtures (and when you should use each).

🎉 Enhancements

For implementors of custom reporters:

  • #​4409: Parallel mode and custom reporter improvements (@​boneskull):
    • Support custom worker-process-only reporters (Runner.prototype.workerReporter()); reporters should subclass ParallelBufferedReporter in mocha/lib/nodejs/reporters/parallel-buffered
    • Allow opt-in of object reference matching for "sufficiently advanced" custom reporters (Runner.prototype.linkPartialObjects()); use if strict object equality is needed when consuming Runner event data
    • Enable detection of parallel mode (Runner.prototype.isParallelMode())

🐛 Fixes

  • #​4476: Workaround for profoundly bizarre issue affecting npm v6.x causing some of Mocha's deps to be installed when mocha is present in a package's devDependencies and npm install --production is run the package's working copy (@​boneskull)
  • #​4465: Worker processes guaranteed (as opposed to "very likely") to exit before Mocha does; fixes a problem when using nyc with Mocha in parallel mode (@​boneskull)
  • #​4419: Restore lookupFiles() in mocha/lib/utils, which was broken/missing in Mocha v8.1.0; it now prints a deprecation warning (use const {lookupFiles} = require('mocha/lib/cli') instead) (@​boneskull)

Thanks to @​AviVahl, @​donghoon-song, @​ValeriaVG, @​znarf, @​sujin-park, and @​majecty for other helpful contributions!

v8.1.3

Compare Source

🐛 Fixes

  • #​4425: Restore Mocha.utils.lookupFiles() and Webpack compatibility (both broken since v8.1.0); Mocha.utils.lookupFiles() is now deprecated and will be removed in the next major revision of Mocha; use require('mocha/lib/cli').lookupFiles instead (@​boneskull)

v8.1.2

Compare Source

🐛 Fixes

🔒 Security Fixes

📖 Documentation

v8.1.1

Compare Source

🐛 Fixes

  • #​4394: Fix regression wherein certain reporters did not correctly detect terminal width (@​boneskull)

v8.1.0

Compare Source

In this release, Mocha now builds its browser bundle with Rollup and Babel, which will provide the project's codebase more flexibility and consistency.

While we've been diligent about backwards compatibility, it's possible consumers of the browser bundle will encounter differences (other than an increase in the bundle size). If you do encounter an issue with the build, please report it here.

This release does not drop support for IE11.

Other community contributions came from @​Devjeel, @​Harsha509 and @​sharath2106. Thank you to everyone who contributed to this release!

Do you read Korean? See this guide to running parallel tests in Mocha, translated by our maintainer, @​outsideris.

🎉 Enhancements

🐛 Fixes

🔒 Security Fixes

📖 Documentation & Website

🔩 Other

  • #​4293: Use Rollup and Babel in build pipeline; add source map to published files (@​Munter)

v8.0.1

Compare Source

The obligatory patch after a major.

🐛 Fixes

v8.0.0

Compare Source

In this major release, Mocha adds the ability to run tests in parallel. Better late than never! Please note the breaking changes detailed below.

Let's welcome @​giltayar and @​nicojs to the maintenance team!

💥 Breaking Changes

  • #​4164: Mocha v8.0.0 now requires Node.js v10.12.0 or newer. Mocha no longer supports the Node.js v8.x line ("Carbon"), which entered End-of-Life at the end of 2019 (@​UlisesGascon)

  • #​4175: Having been deprecated with a warning since v7.0.0, mocha.opts is no longer supported (@​juergba)

    ✨ WORKAROUND: Replace mocha.opts with a configuration file.

  • #​4260: Remove enableTimeout() (this.enableTimeout()) from the context object (@​craigtaub)

    ✨ WORKAROUND: Replace usage of this.enableTimeout(false) in your tests with this.timeout(0).

  • #​4315: The spec option no longer supports a comma-delimited list of files (@​juergba)

    ✨ WORKAROUND: Use an array instead (e.g., "spec": "foo.js,bar.js" becomes "spec": ["foo.js", "bar.js"]).

  • #​4309: Drop support for Node.js v13.x line, which is now End-of-Life (@​juergba)

  • #​4282: --forbid-only will throw an error even if exclusive tests are avoided via --grep or other means (@​arvidOtt)

  • #​4223: The context object's skip() (this.skip()) in a "before all" (before()) hook will no longer execute subsequent sibling hooks, in addition to hooks in child suites (@​juergba)

  • #​4178: Remove previously soft-deprecated APIs (@​wnghdcjfe):

    • Mocha.prototype.ignoreLeaks()
    • Mocha.prototype.useColors()
    • Mocha.prototype.useInlineDiffs()
    • Mocha.prototype.hideDiff()

🎉 Enhancements

📖 Documentation

🔩 Other

🐛 Fixes

(All bug fixes in Mocha v8.0.0 are also breaking changes, and are listed above)

sinonjs/sinon

v13.0.1

Compare Source

  • ec4223f9
    Bump nise to fix sinonjs/nise#​193 (Carl-Erik Kopseng)
  • f329a010
    Add unimported to workflow (#​2441) (Morgan Roderick)
  • 7f16cec9
    Enable updates to same major version (Carl-Erik Kopseng)
  • f784d7ad
    Re-introduce new version.sh script to version hook (Joel Bradshaw)

    This was inadvertently removed during merge conflicts, and is required
    for any of the new release process stuff to work

  • 51c508ab
    Add dry run mode to npm version (#​2436) (Joel Bradshaw)

    • Add DRY_RUN flag to skip publish/push

    • Allow overriding branch names for testing

  • 05341dcf
    Update npm version scripts to manage new releases branch (Joel Bradshaw)
  • fe658261
    Remove release archives from master (Joel Bradshaw)

    These archives made it difficult to find things in the GitHub interface,
    and take up a lot of space in a checked-out repo for something that is
    not useful to most people checking out the repository.

    The main purpose of these archives is to make old versions and
    documentation available on the Sinon website that is run out of this
    repo. This can be supported by using a separate branch for website
    releases, and to maintain the archives.

    Following this commit, the npm version scripts will be updated to
    automatically handle archiving the releases in the new releases branch
    and keeping it up to date with master.

    Also remove the directories we removed from .prettierignore, since they
    don't exist any more.

Released by Carl-Erik Kopseng on 2022-02-01.

v13.0.0

Compare Source

  • cf3d6c0c
    Upgrade packages (#​2431) (Carl-Erik Kopseng)

    • Update all @​sinonjs/ packages

    • Upgrade to fake-timers 9

    • chore: ensure always using latest LTS release

  • 41710467
    Adjust deploy scripts to archive old releases in a separate branch, move existing releases out of master (#​2426) (Joel Bradshaw)

    Co-authored-by: Carl-Erik Kopseng carlerik@gmail.com

  • c80a7266
    Bump node-fetch from 2.6.1 to 2.6.7 (#​2430) (dependabot[bot])

    Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@​users.noreply.github.com>

  • a00f14a9
    Add explicit export for ./* (#​2413) (なつき)
  • b82ca7ad
    Bump cached-path-relative from 1.0.2 to 1.1.0 (#​2428) (dependabot[bot])
  • a9ea1427
    Add documentation for assert.calledOnceWithMatch (#​2424) (Mathias Schreck)
  • 1d5ab86b
    Be more general in stripping off stack frames to fix Firefox tests (#​2425) (Joel Bradshaw)
  • 56b06129
    Check call count type (#​2410) (Joel Bradshaw)
  • 7863e2df
    Fix #​2414: make Sinon available on homepage (Carl-Erik Kopseng)
  • fabaabdd
    Bump nokogiri from 1.11.4 to 1.13.1 (#​2423) (dependabot[bot])
  • dbc0fbd2
    Bump shelljs from 0.8.4 to 0.8.5 (#​2422) (dependabot[bot])
  • fb8b3d72
    Run Prettier (Carl-Erik Kopseng)
  • 12a45939
    Fix 2377: Throw error when trying to stub non-configurable or non-writable properties (#​2417) (Stuart Dotson)

    Fixes issue #​2377 by throwing an error when trying to stub non-configurable or non-writable properties

Released by Carl-Erik Kopseng on 2022-01-28.

v12.0.1

Compare Source

  • 3f598221
    Fix issue with npm unlink for npm version > 6 (Carl-Erik Kopseng)
  • 51417a38
    Fix bundling of cjs module (#​2412) (Julian Grinblat)

Released by Carl-Erik Kopseng on 2021-11-04.

v12.0.0

Compare Source

  • b20ef9e4
    Upgrade to fake-timers@8 (Carl-Erik Kopseng). This is potentially breaking, but should not be,
    as the breaking change deals with the Node timer object created by fake timers.
  • eba42cc3
    Enable esm named exports (#​2382) (Julian Grinblat)
  • b0cf5448
    Spelling (#​2398) (Josh Soref)
  • e78a6706
    Make calledWith() assertions idempotent (#​2407) (Joel Bradshaw)
  • 2814c0a2
    Generate CHANGES.md using @​studio/changes (Morgan Roderick)

    This will bring us closer to having the same release process as the
    other @sinonjs packages.

  • 2d5d6ad4
    Run tests in Node 16 in GitHub Actions (Morgan Roderick)

Released by Carl-Erik Kopseng on 2021-11-03.

v11.1.2

Compare Source

v11.1.1

Compare Source

  • Fix #​2379 by using v7 of supports-color

v11.1.0

Compare Source

  • Add sinon.promise() implementation (#​2369)
  • Set wrappedMethod on getters/setters (#​2378)
  • [Docs] Update fake-server usage & descriptions (#​2365)
  • Fake docs improvement (#​2360)
  • Update nise to 5.1.0 (fixed #​2318)

v11.0.0

Compare Source

  • Explicitly use samsam 6.0.2 with fix for #​2345
  • Update most packages (#​2371)
  • Update compatibility docs (#​2366)
  • Update packages (includes breaking fake-timers change, see #​2352)
  • Warn of potential memory leaks (#​2357)
  • Fix clock test errors

v10.0.1

Compare Source

  • Upgrade sinon components (bumps y18n to 4.0.1)
  • Bump y18n from 4.0.0 to 4.0.1

v10.0.0

Compare Source

v9.2.4

Compare Source

v9.2.3

Compare Source

v9.2.2

Compare Source

v9.2.1

Compare Source

  • Fix #​2203: skip writing 'name' property if not writable (#​2304)
  • Update error message on assert when representation of expected and actual value is equal, fixing issue #​2084 (#​2303)
  • Make sandboxes each use their own assert object (#​2302)
  • Add usingPromise() method on fakes to fix issue #​2293 (#​2301)

v9.2.0

Compare Source

  • Update dependencies (#​2299)
  • Update sandbox docs with missing comma
  • Add minor markdown formatting to release docs for sandbox
  • Minor formatting improvements to legacy sandbox documentation

v9.1.0

Compare Source

  • Add a calledOnceWithMatch assertion (#​2294)

v9.0.3

Compare Source

v9.0.2

Compare Source

v9.0.1

Compare Source

  • Fix #​2226: restore props defined on prototype chain by deleting

v9.0.0

Compare Source

  • Ignore errors on thisValue property accesses (#​2216)
  • Add firstArg to spy calls and fakes. (#​2150)
  • Drop Node 8 support
TypeStrong/ts-node

v10.4.0

Compare Source

Added

  • Adds support for targets "es2020" and "es2021" to swc transpiler (#​1521)
  • Adds automatic target downgrade when using older versions of swc (#​1521)
    • If tsconfig specifies es2020, but your version of swc only supports up to es2019, ts-node will automatically switch to es2019 instead of throwing an error

Changed

Fixed

https://github.com/TypeStrong/ts-node/milestone/8

v10.3.1

Compare Source

Fixed

https://github.com/TypeStrong/ts-node/milestone/7

v10.3.0

Compare Source

Questions about this release? Ask in the official discussion thread: #​1507

Added

  • Declare types for node builtin modules within REPL so you do not need to import them (#​1424, #​1500)
    • Node REPL exposes builtin modules as globals; typechecker now understands this
    • Typechecking should no longer raise errors when using builtins without first importing
    • For example: util.promisify(setTimeout)(1000) or fs.readFileSync('example.txt')
  • Add createEsmHooks() function to create ESM loader hooks (API docs) (#​1439) @​nonara
    • Can be used to compose our loader hooks with another loader or additional logic
  • register() accepts a ts-node Service (API docs) (#​1474)
    • register(options) is still supported; no breaking changes
  • Add support for Node.js's new loader hooks API (#​1372, #​1457, #​1007) @​jonaskello
    • Node.js has changed their loader hooks API
    • ts-node is compatible with all node versions, detects your node version and exposes the correct hooks API
    • Node's new API currently only available in node v17 nightly builds
    • Node will eventually backport the changes to node 16, and may also be backport to 14 and 12
  • Add --emit to --help output (#​1400, #​1484) @​markbradley27

Changed

  • When ts-node is registered and other libraries require('source-map-support'), they will be redirected to @cspotcode/source-map-support
    • See complete description in Fixed section below

Fixed

  • Fix #​1440, #​1441, #​1438, #​1495: Incorrect stack traces when third-party libraries use source-map-support instead of @cspotcode/source-map-support (#​1440, #​1441, #​1438, #​1495, cspotcode/node-source-map-support#​23, #​1496, #​1497) @​ejose19
    • When ts-node is registered and other libraries require('source-map-support'), they will be redirected to @cspotcode/source-map-support
    • ts-node uses @cspotcode/source-map-support for the fixes and enhancements listed here: @cspotcode/source-map-support changelog
    • To ensure correct stack traces, all libraries must share a compatible sourcemap support implementation
  • Fix #​1363: REPL may erroneously combine previous input with next input, eval both as a single statement (#​1363, #​1480) @​TheUnlocked
    • For example, entering 100 on first line and * 2 on second line would erronously be interpreted as 100 * 2
    • REPL now ensures both lines are separate statements, both when typechecking and when evaluating
  • Fix #​1488: Node may log "circular dependency" warning when using allowJs (#​1488, #​1489)
  • Fix #​1301: Filter empty strings from TS_NODE_IGNORE and TS_NODE_IGNORE_DIAGNOSTICS; treat empty environment variable as empty array (#​1301, #​1483) @​ValeriaVG
    • TS_NODE_IGNORE= ts-node ./example.ts will disable default ignore rules; will compile files in ./node_modules

Docs

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@vkolgi vkolgi merged commit b5ec1f0 into master Feb 3, 2022
@renovate renovate bot deleted the renovate/major-dev-dependencies branch February 3, 2022 07:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dev-dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@vkolgi @renovate-bot