[Snyk] Upgrade mitt from 1.1.3 to 3.0.1

[q1blue]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade mitt from 1.1.3 to 3.0.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

Warning: This is a major version upgrade, and may be a breaking change.

• The recommended version is 6 versions ahead of your current version.
• The recommended version was released 7 months ago, on 2023-07-04.

Release notes

Package name: mitt

• 3.0.1 - 2023-07-04
  

  What's Changed

  • chore: fix typescript issue with NodeNext, fix #166 by @ Mister-Hope in #167

  New Contributors

  • @ Mister-Hope made their first contribution in #167

  Full Changelog: 3.0.0...3.0.1

• 3.0.0 - 2021-06-23
  

  Mitt 3.0 adds a couple nice new features.

  1. Remove all handlers of a type:

  Calling .off("type") with no handler argument now removes all listeners of that type (#123, #124, #129 - thanks @ sealice!).

  2. New, stronger typing:

  It's now possible to define explicit types for events and their arguments (#114, thanks @ iyegoroff & @ deskoh):

  import mitt from 'mitt';
  const events = mitt<{ foo: string }>();
  events.on('foo', e => {});  // `e` is inferred to be of type string!
  events.emit('foo', 42);  // TypeError: got a number, expected a string

  3. Package Exports:

  As of 3.0.0, the mitt package now uses Package Exports. This shouldn't change usage or anything, it just means you're more likely to end up using the ES Module version of Mitt when running in Node.

• 2.1.0 - 2020-07-15
  

  Mitt 2 is out of preview!

  • It's written in TypeScript and ships type definitions (#107, thanks again @ jackfranklin!)

  • Event handlers are now stored in a Map instead of an Object.

    Upgrading: If you aren't passing an object to mitt({}), version 2 is backwards-compatible.
    If you were, turn your object into a map:

    -const handlers = {
    - foo: [() => alert(1)]
    -};
    +const handlers = new Map();
    +handlers.set('foo', [() => alert(1)]);

    const events = mitt(handlers);

  • The event handler Map is now exposed as .all: (#105, thanks @ jaylinski!)

    const events = mitt();
    events.on('foo', () => alert(1));
    events.on('bar', () => alert(2));

    // access handlers directly if needed:
    events.all.get('foo') // [() => alert(1)]

    // remove all event handlers:
    events.all.clear();

• 2.0.1 - 2020-05-27
  

  This patch update for the 2.0 prerelease fixes missing type exports (#101).
  It also reduces size and improves performance (#100).

• 2.0.0 - 2020-05-26
  

  Possible Breaking Change: mitt() previously accepted an optional Object "event map" argument. In 2.0.0, events are stored in an actual JavaScript Map rather than as properties on a plain object:

  - const map = {};
  + const map = new Map();

const events = mitt(map);
const foo = () => {};
events.on('foo', foo);

- map.foo // [foo];
+ map.get('foo') // [foo];

Now the good news: if you weren't using this argument, mitt@2 isn't a breaking change for you.

Also, Mitt is now written in TypeScript! Huge thanks to @ jackfranklin for doing all the work including setting up a much nicer build toolchain.

1.2.0 - 2019-10-21

It's Mitt's first release since 2017! That's the thing about a 200 byte library - there's not a lot of code here to necessitate constant updates. Take it as a sign of stability.

This release is primarily an improvement to the TypeScript definition we ship with Mitt:

• You can now invoke mitt() with or without new in TypeScript (#60/#67 - thanks @ davidkpiano)
• .on('*', handler) now has types that pass the correct (event, data) arguments (#76, thanks @ zbuttram)
• The optional all parameter, which lets you pass your own mapping of handler Arrays to Mitt, now has correct types (#73, thanks @ jesperzach)

1.1.3 - 2017-12-07

• Fix handler removal (.off()) during emit (#65, thanks @ sqal & @ farskid)
• Fix emit and EventHandler type annotations (#47, thanks @ rvikmanis)
• more precise type annotation for WildCardEventHandler (#58, thanks @ tungv)

from mitt GitHub release notes

Commit messages

Package name: mitt

• b240473 3.0.1
• 05f4ce6 apply prettier formatting to all files
• 3f81679 fix TypeScript config
• bbba04a move eslint config out of package.json and add prettier
• 5a17bef update deps
• 1194efb Update package.json (Need a way to require a single port BrowserSync/browser-sync#167)
• f9a0b53 Clarify what `off('*')` does
• 13905bd 3.0.0
• f3990ec Add Package Exports configuration (Filename of client script BrowserSync/browser-sync#139)
• ec0aab7 update actions for main branch
• c580f81 Merge branch 'andreiTn-patch-1'
• 9539abe Merge master
• 0cce8fa Add test for Cookies BrowserSync/browser-sync#124
• 4cce9cb Add support for mitt.off("type"), which removes all handlers of a given type
• 53eb689 Merge branch 'master' into patch_123
• f0f36b0 Add LICENSE file
• 62a2351 Remove "src" from published files list (fixes Properly merge array config values BrowserSync/browser-sync#128)
• 7872a47 Merge branch 'cheaper' of https://github.com/sealice/mitt into sealice-cheaper
• 8f439b8 Stronger typing (Proxy doesn't work with subdirectories BrowserSync/browser-sync#114)
• 2d59261 compression code
• ec9122b Fix the format and update the off API
• 5f2ccef Add new features of emitter.off. Fixes Styles go away when reloading BrowserSync/browser-sync#123
• 22c5dcb 2.1.0
• 0f41ead Merge branch 'expose-all' of https://github.com/jaylinski/mitt

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[changeset-bot]

⚠️ No Changeset found

Latest commit: d40d8ad

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR