Skip to content
This repository has been archived by the owner on Mar 13, 2023. It is now read-only.

Update external-non-major (external non-major bumps) #5

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update external-non-major (external non-major bumps) #5

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 27, 2022 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@commitlint/cli (source) ^12.1.1 -> ^12.1.4 age adoption passing confidence
@commitlint/config-conventional (source) ^12.1.1 -> ^12.1.4 age adoption passing confidence
@types/cors (source) ^2.8.10 -> ^2.8.13 age adoption passing confidence
@types/node (source) ^16.11.36 -> ^16.18.15 age adoption passing confidence
@vitejs/plugin-vue (source) ^2.3.3 -> ^2.3.4 age adoption passing confidence
nodemon (source) ^2.0.7 -> ^2.0.21 age adoption passing confidence
pinia ^2.0.14 -> ^2.0.33 age adoption passing confidence
pino-pretty ^8.0.0 -> ^8.1.0 age adoption passing confidence
socket.io ^4.5.1 -> ^4.6.1 age adoption passing confidence
socket.io-client ^4.5.1 -> ^4.6.1 age adoption passing confidence
ts-node (source) ^10.8.1 -> ^10.9.1 age adoption passing confidence
typescript (source) ~4.7.2 -> ~4.9.5 age adoption passing confidence
vue (source) ^3.2.36 -> ^3.2.47 age adoption passing confidence
vue-router ^4.0.15 -> ^4.1.6 age adoption passing confidence

Release Notes

vitejs/vite-plugin-vue

v2.3.4

Compare Source

remy/nodemon

v2.0.21

Compare Source

Bug Fixes

v2.0.20

Compare Source

Bug Fixes
  • remove postinstall script (e099e91)

v2.0.19

Compare Source

Bug Fixes

v2.0.18

Compare Source

Bug Fixes
  • revert update-notifier forcing esm (1b3bc8c)

v2.0.17

Compare Source

Bug Fixes
vuejs/pinia

v2.0.33

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.32

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.31

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.30

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.29

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.28

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.27

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.26

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.25

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.24

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.23

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.22

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.21

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.20

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.19

Compare Source

v2.0.18

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.17

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.16

Compare Source

Please refer to CHANGELOG.md for details.

v2.0.15

Compare Source

Please refer to CHANGELOG.md for details.

pinojs/pino-pretty

v8.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino-pretty@v8.0.0...v8.1.0

socketio/socket.io

v4.6.1

Compare Source

Bug Fixes
  • properly handle manually created dynamic namespaces (0d0a7a2)
  • types: fix nodenext module resolution compatibility (#​4625) (d0b22c6)
Dependencies

v4.6.0

Compare Source

Bug Fixes
  • add timeout method to remote socket (#​4558) (0c0eb00)
  • typings: properly type emits with timeout (f3ada7d)
Features
Promise-based acknowledgements

This commit adds some syntactic sugar around acknowledgements:

  • emitWithAck()
try {
  const responses = await io.timeout(1000).emitWithAck("some-event");
  console.log(responses); // one response per client
} catch (e) {
  // some clients did not acknowledge the event in the given delay
}

io.on("connection", async (socket) => {
    // without timeout
  const response = await socket.emitWithAck("hello", "world");

  // with a specific timeout
  try {
    const response = await socket.timeout(1000).emitWithAck("hello", "world");
  } catch (err) {
    // the client did not acknowledge the event in the given delay
  }
});
  • serverSideEmitWithAck()
try {
  const responses = await io.timeout(1000).serverSideEmitWithAck("some-event");
  console.log(responses); // one response per server (except itself)
} catch (e) {
  // some servers did not acknowledge the event in the given delay
}

Added in 184f3cf.

Connection state recovery

This feature allows a client to reconnect after a temporary disconnection and restore its state:

  • id
  • rooms
  • data
  • missed packets

Usage:

import { Server } from "socket.io";

const io = new Server({
  connectionStateRecovery: {
    // default values
    maxDisconnectionDuration: 2 * 60 * 1000,
    skipMiddlewares: true,
  },
});

io.on("connection", (socket) => {
  console.log(socket.recovered); // whether the state was recovered or not
});

Here's how it works:

  • the server sends a session ID during the handshake (which is different from the current id attribute, which is public and can be freely shared)
  • the server also includes an offset in each packet (added at the end of the data array, for backward compatibility)
  • upon temporary disconnection, the server stores the client state for a given delay (implemented at the adapter level)
  • upon reconnection, the client sends both the session ID and the last offset it has processed, and the server tries to restore the state

The in-memory adapter already supports this feature, and we will soon update the Postgres and MongoDB adapters. We will also create a new adapter based on Redis Streams, which will support this feature.

Added in 54d5ee0.

Compatibility (for real) with Express middlewares

This feature implements middlewares at the Engine.IO level, because Socket.IO middlewares are meant for namespace authorization and are not executed during a classic HTTP request/response cycle.

Syntax:

io.engine.use((req, res, next) => {
  // do something

  next();
});

// with express-session
import session from "express-session";

io.engine.use(session({
  secret: "keyboard cat",
  resave: false,
  saveUninitialized: true,
  cookie: { secure: true }
}));

// with helmet
import helmet from "helmet";

io.engine.use(helmet());

A workaround was possible by using the allowRequest option and the "headers" event, but this feels way cleaner and works with upgrade requests too.

Added in 24786e7.

Error details in the disconnecting and disconnect events

The disconnect event will now contain additional details about the disconnection reason.

io.on("connection", (socket) => {
  socket.on("disconnect", (reason, description) => {
    console.log(description);
  });
});

Added in 8aa9499.

Automatic removal of empty child namespaces

This commit adds a new option, "cleanupEmptyChildNamespaces". With this option enabled (disabled by default), when a socket disconnects from a dynamic namespace and if there are no other sockets connected to it then the namespace will be cleaned up and its adapter will be closed.

import { createServer } from "node:http";
import { Server } from "socket.io";

const httpServer = createServer();
const io = new Server(httpServer, {
  cleanupEmptyChildNamespaces: true
});

Added in 5d9220b.

A new "addTrailingSlash" option

The trailing slash which was added by default can now be disabled:

import { createServer } from "node:http";
import { Server } from "socket.io";

const httpServer = createServer();
const io = new Server(httpServer, {
  addTrailingSlash: false
});

In the example above, the clients can omit the trailing slash and use /socket.io instead of /socket.io/.

Added in d0fd474.

Performance Improvements
  • precompute the WebSocket frames when broadcasting (da2b542)
Dependencies

v4.5.4

Compare Source

This release contains a bump of:

Dependencies

v4.5.3

Compare Source

Bug Fixes
  • typings: accept an HTTP2 server in the constructor (d3d0a2d)
  • typings: apply types to "io.timeout(...).emit()" calls (e357daf)

v4.5.2

Compare Source

Bug Fixes
  • prevent the socket from joining a room after disconnection (18f3fda)
  • uws: prevent the server from crashing after upgrade (ba497ee)
socketio/socket.io-client

v4.6.1

Compare Source

Bug Fixes
  • do not drain the queue while the socket is offline (4996f9e)
  • prevent duplicate connections when multiplexing (46213a6)
Dependencies

v4.6.0

Compare Source

Bug Fixes
  • typings: do not expose browser-specific types (4d6d95e)
  • ensure manager.socket() returns an active socket (b7dd891)
  • typings: properly type emits with timeout (#​1570) (33e4172)
Features
A new "addTrailingSlash" option

The trailing slash which was added by default can now be disabled:

import { io } from "socket.io-client";

const socket = io("https://example.com", {
  addTrailingSlash: false
});

In the example above, the request URL will be https://example.com/socket.io instead of https://example.com/socket.io/.

Added in 21a6e12.

Promise-based acknowledgements

This commit adds some syntactic sugar around acknowledgements:

// without timeout
const response = await socket.emitWithAck("hello", "world");

// with a specific timeout
try {
  const response = await socket.timeout(1000).emitWithAck("hello", "world");
} catch (err) {
  // the server did not acknowledge the event in the given delay
}

Note: environments that do not support Promises will need to add a polyfill in order to use this feature.

Added in 47b979d.

Connection state recovery

This feature allows a client to reconnect after a temporary disconnection and restore its ID and receive any packets that was missed during the disconnection gap. It must be enabled on the server side.

A new boolean attribute named recovered is added on the socket object:

socket.on("connect", () => {
  console.log(socket.recovered); // whether the recovery was successful
});

Added in 54d5ee0 (server) and b4e20c5 (client).

Retry mechanism

Two new options are available:

  • retries: the maximum number of retries. Above the limit, the packet will be discarded.
  • ackTimeout: the default timeout in milliseconds used when waiting for an acknowledgement (not to be mixed up with the already existing timeout option, which is used by the Manager during the connection)
const socket = io({
  retries: 3,
  ackTimeout: 10000
});

// implicit ack
socket.emit("my-event");

// explicit ack
socket.emit("my-event", (err, val) => { /* ... */ });

// custom timeout (in that case the ackTimeout is optional)
socket.timeout(5000).emit("my-event", (err, val) => { /* ... */ });

In all examples above, "my-event" will be sent up to 4 times (1 + 3), until the server sends an acknowledgement.

Assigning a unique ID to each packet is the duty of the user, in order to allow deduplication on the server side.

Added in 655dce9.

Dependencies

v4.5.4

Compare Source

This release contains a bump of the socket.io-parser dependency, in order to fix CVE-2022-2421.

Dependencies

v4.5.3

Compare Source

Bug Fixes
  • do not swallow user exceptions (2403b88)

v4.5.2

Compare Source

Bug Fixes
  • handle ill-formatted packet from server (c597023)
TypeStrong/ts-node

v10.9.1

Compare Source

Fixed

  • Workaround nodejs bug introduced in 18.6.0 (#​1838) @​cspotcode
    • Only affects projects on node >=18.6.0 using --esm
    • Older versions of node and projects without --esm are unaffected

https://github.com/TypeStrong/ts-node/milestone/18?closed=1

v10.9.0

Compare Source

Added

  • --project accepts path to a directory containing a tsconfig.json (#​1829, #​1830) @​cspotcode
    • previously it required an explicit filename
  • Added helpful error message when swc version is too old to support our configuration (#​1802) @​cspotcode
  • Added experimentalTsImportSpecifiers option which allows using voluntary .ts file extensions in import specifiers (undocumented except for API docs) (#​1815) @​cspotcode

Fixed

https://github.com/TypeStrong/ts-node/milestone/16?closed=1

v10.8.2

Compare Source

Fixed

  • Revert "Use file URL for source map paths" (#​1821) @​cspotcode
    • Fixes #​1790: ts-node 10.8.1 regression where nyc code coverage reports had incorrect paths
    • Fixes #​1797: ts-node 10.8.1 regression where breakpoints did not hit in VSCode debugging
  • Allow JSON imports in node 16.15 and up (#​1792) @​queengooborg
    • JSON imports were already supported in v17.5 and up
    • this change extends support to >=16.15.0,<17.0.0
    • These version ranges match vanilla node's support for JSON imports

https://github.com/TypeStrong/ts-node/milestone/15?closed=1

Microsoft/TypeScript

v4.9.5: TypeScript 4.9.5

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

Changes:

v4.9.4: TypeScript 4.9.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

Changes:

This list of changes was auto generated.

v4.9.3: TypeScript 4.9

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

Changes:

See More

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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, check this box

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

@renovate renovate bot force-pushed the renovate/external-non-major branch from 20e8c39 to 84330c5 Compare June 27, 2022 11:07
@renovate renovate bot changed the title Update external-non-major (external non-major bumps) Update: update external-non-major (external non-major bumps) Jun 27, 2022
@renovate renovate bot changed the title Update: update external-non-major (external non-major bumps) Update external-non-major (external non-major bumps) Jun 28, 2022
@renovate renovate bot force-pushed the renovate/external-non-major branch 6 times, most recently from ef558c2 to 23e95f8 Compare July 4, 2022 13:32
@renovate renovate bot force-pushed the renovate/external-non-major branch 7 times, most recently from c48cfc1 to 1293a47 Compare July 11, 2022 15:47
@renovate renovate bot force-pushed the renovate/external-non-major branch 5 times, most recently from 3ee1f6b to 41d41ee Compare July 15, 2022 23:14
@renovate renovate bot force-pushed the renovate/external-non-major branch 4 times, most recently from fb709d9 to 35e97b4 Compare July 30, 2022 22:48
@renovate renovate bot force-pushed the renovate/external-non-major branch 3 times, most recently from a5d6027 to e7a1cac Compare August 12, 2022 14:08
@renovate renovate bot force-pushed the renovate/external-non-major branch 7 times, most recently from 01e5f49 to 1ebb864 Compare August 22, 2022 15:51
@renovate renovate bot force-pushed the renovate/external-non-major branch 6 times, most recently from 6a64221 to d6e35a7 Compare August 26, 2022 13:33
@renovate renovate bot force-pushed the renovate/external-non-major branch 4 times, most recently from 8549a40 to 738b4c4 Compare September 6, 2022 09:36
@renovate renovate bot force-pushed the renovate/external-non-major branch 3 times, most recently from 414637a to ab3be27 Compare September 8, 2022 19:35
@renovate renovate bot force-pushed the renovate/external-non-major branch from ab3be27 to d42e3ab Compare September 25, 2022 19:11
@renovate renovate bot force-pushed the renovate/external-non-major branch from d42e3ab to 1b2a083 Compare November 20, 2022 17:55
@renovate renovate bot force-pushed the renovate/external-non-major branch from 1b2a083 to 4082192 Compare March 12, 2023 17:56
@renovate renovate bot force-pushed the renovate/external-non-major branch from 4082192 to 2a94dbb Compare March 13, 2023 19:53
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@renovate-approve renovate-approve[bot] renovate-approve[bot] approved these changes

Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants