serwist

Patch Changes

• Updated dependencies []:
  • @serwist/[email protected]

Patch Changes

• Updated dependencies []:
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]

Patch Changes

• Updated dependencies []:
  • @serwist/[email protected]

Patch Changes

• Updated dependencies []:
  • @serwist/[email protected]

Patch Changes

• Updated dependencies []:
  • @serwist/[email protected]

Patch Changes

• Updated dependencies []:
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]

Patch Changes

• Updated dependencies []:
  • @serwist/[email protected]

Patch Changes

• Updated dependencies []:
  • @serwist/[email protected]

Major Changes

• ea0944c Thanks @DuCanhGH! - refactor: use iterables

  • Serwist now uses iterables in its code. For instance, Headers.prototype.entries() can be noticed at parts of @serwist/cacheable-response.
  • This is partly thanks to our Node.js requirement being bumped to 18.0.0. Iterables have been supported in all major browsers for ages, so they wouldn't be a problem (hell, all browsers that support service workers have support for iterables).
  • Still, since this requires us to enforce the use of Node.js 18.0.0 or later, it is marked a breaking change.

Patch Changes

• Updated dependencies [ea0944c]:
  • @serwist/[email protected]

Major Changes

• ea0944c Thanks @DuCanhGH! - refactor: use iterables

  • Serwist now uses iterables in its code. For instance, Headers.prototype.entries() can be noticed at parts of @serwist/cacheable-response.
  • This is partly thanks to our Node.js requirement being bumped to 18.0.0. Iterables have been supported in all major browsers for ages, so they wouldn't be a problem (hell, all browsers that support service workers have support for iterables).
  • Still, since this requires us to enforce the use of Node.js 18.0.0 or later, it is marked a breaking change.

Minor Changes

• 4de5675 Thanks @DuCanhGH! - refactor(webpack,next): allow webpack to be an optional peerDependency

  • Since we support frameworks that ship a prebundled webpack, such as Next.js, it would be nice if we can take advantage of that as well.

  • As a result, webpack is now an optional peerDependency for @serwist/webpack-plugin and is no longer a peerDependency for @serwist/next. Thanks to the fact that we currently don't use any webpack plugin, it is also not indirectly installed.

Patch Changes

• Updated dependencies [ea0944c]:
  • @serwist/[email protected]

Major Changes

• ea0944c Thanks @DuCanhGH! - refactor: use iterables

  • Serwist now uses iterables in its code. For instance, Headers.prototype.entries() can be noticed at parts of @serwist/cacheable-response.
  • This is partly thanks to our Node.js requirement being bumped to 18.0.0. Iterables have been supported in all major browsers for ages, so they wouldn't be a problem (hell, all browsers that support service workers have support for iterables).
  • Still, since this requires us to enforce the use of Node.js 18.0.0 or later, it is marked a breaking change.

Patch Changes

• Updated dependencies [ea0944c, ea0944c]:
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]

Major Changes

• ea0944c Thanks @DuCanhGH! - refactor: use iterables

  • Serwist now uses iterables in its code. For instance, Headers.prototype.entries() can be noticed at parts of @serwist/cacheable-response.
  • This is partly thanks to our Node.js requirement being bumped to 18.0.0. Iterables have been supported in all major browsers for ages, so they wouldn't be a problem (hell, all browsers that support service workers have support for iterables).
  • Still, since this requires us to enforce the use of Node.js 18.0.0 or later, it is marked a breaking change.

Patch Changes

• Updated dependencies [ea0944c]:
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]

Major Changes

• ea0944c Thanks @DuCanhGH! - refactor: use iterables

  • Serwist now uses iterables in its code. For instance, Headers.prototype.entries() can be noticed at parts of @serwist/cacheable-response.
  • This is partly thanks to our Node.js requirement being bumped to 18.0.0. Iterables have been supported in all major browsers for ages, so they wouldn't be a problem (hell, all browsers that support service workers have support for iterables).
  • Still, since this requires us to enforce the use of Node.js 18.0.0 or later, it is marked a breaking change.

Patch Changes

• Updated dependencies [ea0944c]:
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]

Major Changes

• ea0944c Thanks @DuCanhGH! - refactor: use iterables

  • Serwist now uses iterables in its code. For instance, Headers.prototype.entries() can be noticed at parts of @serwist/cacheable-response.
  • This is partly thanks to our Node.js requirement being bumped to 18.0.0. Iterables have been supported in all major browsers for ages, so they wouldn't be a problem (hell, all browsers that support service workers have support for iterables).
  • Still, since this requires us to enforce the use of Node.js 18.0.0 or later, it is marked a breaking change.

Patch Changes

• Updated dependencies [ea0944c]:
  • @serwist/[email protected]
  • @serwist/[email protected]

Major Changes

• ea0944c Thanks @DuCanhGH! - refactor: use iterables

  • Serwist now uses iterables in its code. For instance, Headers.prototype.entries() can be noticed at parts of @serwist/cacheable-response.
  • This is partly thanks to our Node.js requirement being bumped to 18.0.0. Iterables have been supported in all major browsers for ages, so they wouldn't be a problem (hell, all browsers that support service workers have support for iterables).
  • Still, since this requires us to enforce the use of Node.js 18.0.0 or later, it is marked a breaking change.

Patch Changes

• Updated dependencies [ea0944c]:
  • @serwist/[email protected]

Major Changes

• ea0944c Thanks @DuCanhGH! - refactor: use iterables

  • Serwist now uses iterables in its code. For instance, Headers.prototype.entries() can be noticed at parts of @serwist/cacheable-response.
  • This is partly thanks to our Node.js requirement being bumped to 18.0.0. Iterables have been supported in all major browsers for ages, so they wouldn't be a problem (hell, all browsers that support service workers have support for iterables).
  • Still, since this requires us to enforce the use of Node.js 18.0.0 or later, it is marked a breaking change.

Patch Changes

• Updated dependencies [ea0944c]:
  • @serwist/[email protected]

Major Changes

• ea0944c Thanks @DuCanhGH! - refactor: use iterables

  • Serwist now uses iterables in its code. For instance, Headers.prototype.entries() can be noticed at parts of @serwist/cacheable-response.
  • This is partly thanks to our Node.js requirement being bumped to 18.0.0. Iterables have been supported in all major browsers for ages, so they wouldn't be a problem (hell, all browsers that support service workers have support for iterables).
  • Still, since this requires us to enforce the use of Node.js 18.0.0 or later, it is marked a breaking change.

Patch Changes

• Updated dependencies [ea0944c, ea0944c]:
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]

Major Changes

• ea0944c Thanks @DuCanhGH! - refactor: use iterables

  • Serwist now uses iterables in its code. For instance, Headers.prototype.entries() can be noticed at parts of @serwist/cacheable-response.
  • This is partly thanks to our Node.js requirement being bumped to 18.0.0. Iterables have been supported in all major browsers for ages, so they wouldn't be a problem (hell, all browsers that support service workers have support for iterables).
  • Still, since this requires us to enforce the use of Node.js 18.0.0 or later, it is marked a breaking change.

Patch Changes

• Updated dependencies [ea0944c]:
  • @serwist/[email protected]
  • @serwist/[email protected]
  • @serwist/[email protected]

Major Changes

• ea0944c Thanks @DuCanhGH! - refactor: use iterables

  • Serwist now uses iterables in its code. For instance, Headers.prototype.entries() can be noticed at parts of @serwist/cacheable-response.
  • This is partly thanks to our Node.js requirement being bumped to 18.0.0. Iterables have been supported in all major browsers for ages, so they wouldn't be a problem (hell, all browsers that support service workers have support for iterables).
  • Still, since this requires us to enforce the use of Node.js 18.0.0 or later, it is marked a breaking change.

Patch Changes

• Updated dependencies [ea0944c]:
  • @serwist/[email protected]