Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.3.4
->3.9.0
3.0.9
->3.1.9
3.0.9
->3.1.9
0.24.0
->2.0.1
0.24.0
->2.0.0
8.4.4
->9.0.8
8.4.4
->9.0.8
8.4.4
->9.0.8
0.9.2
->0.11.1
20.11.25
->20.16.5
20.11.25
->20.16.5
10.4.18
->10.4.20
1.6.7
->1.7.7
2.1.0
->2.1.1
1.11.10
->1.11.13
7.34.0
->7.36.1
4.18.3
->4.21.0
16.8.1
->16.9.0
6.1.0
->7.1.0
9.0.11
->9.1.6
5.2.3
->5.9.2
15.2.2
->15.2.10
0.2.1
->0.3.0
8.15.4
->9.11.0
8.4.35
->8.4.47
3.2.5
->3.3.3
0.5.12
->0.6.6
7.51.0
->7.53.0
1.4.3
->1.5.0
2.2.1
->2.5.2
3.4.1
->3.4.12
5.4.2
->5.6.2
5.4.2
->5.6.2
3.22.4
->3.23.8
Release Notes
react-hook-form/resolvers (@hookform/resolvers)
v3.9.0
Compare Source
Features
v3.8.0
Compare Source
v3.7.0
Compare Source
Bug Fixes
Features
v3.6.0
Compare Source
Features
v3.5.0
Compare Source
Features
v3.4.2
Compare Source
Bug Fixes
v3.4.1
Compare Source
Bug Fixes
v3.4.0
Compare Source
nhost/nhost (@nhost/nhost-js)
v3.1.9
Compare Source
v3.1.8
Compare Source
v3.1.7
Compare Source
v3.1.6
Compare Source
v3.1.5
Compare Source
v3.1.4
Compare Source
v3.1.3
Compare Source
v3.1.2
Compare Source
v3.1.1
Compare Source
v3.1.0
Compare Source
v3.0.11
Compare Source
v3.0.10
Compare Source
v3.0.9
Compare Source
v3.0.8
Compare Source
v3.0.7
Compare Source
v3.0.6
Compare Source
novuhq/novu (@novu/node)
v2.0.1
Compare Source
v2.0.0
Compare Source
v0.24.2
Compare Source
v0.24.1
Compare Source
serwist/serwist (@serwist/next)
v9.0.8
Compare Source
Patch Changes
ffb64c4
]:v9.0.7
Compare Source
Patch Changes
#192
ceea5d1
Thanks @DuCanhGH! - chore(build): remove extraneous Node.js API wrappersfs-extra
,pathe
,fast-json-stable-stringify
, orupath
, so let's just remove them.Updated dependencies [
ceea5d1
]:v9.0.6
Compare Source
Patch Changes
12f6e82
,1e9cc3c
]:v9.0.5
Compare Source
Patch Changes
v9.0.4
Compare Source
Patch Changes
db66e96
Thanks @DuCanhGH! - chore(deps): monthly dependencies maintenanceUpdated dependencies [
db66e96
]:v9.0.3
Compare Source
Patch Changes
c0d65aa
Thanks @DuCanhGH! - chore(deps): updated all dependenciesUpdated dependencies [
c0d65aa
,c0d65aa
,c0d65aa
]:v9.0.2
Compare Source
Patch Changes
v9.0.1
Compare Source
Patch Changes
#128
ee8fa90
Thanks @DuCanhGH! - fix(next): check if the current page is in the service worker's scope before registeringInjectPartial.scope
was set to some value, and you visited a page out of that scope, you would see the warning "The current page is not in scope for the registered service worker. Was this a mistake?" logged. This simply fixes that by checking if the page is in the scope before callingwindow.serwist.register()
.Updated dependencies []:
v9.0.0
Compare Source
Major Changes
#123
add4fdd
Thanks @DuCanhGH! - refactor(build): moved framework-specific types out of@serwist/build
Types the likes of
WebpackPartial
,WebpackInjectManifestOptions
,ViteInjectManifestOptions
, along with their according validators have been moved out of@serwist/build
.This design, a relic of Workbox, never made any sense in the first place. As such, we are getting rid of it and migrating to a design where types and validators are co-located with their related packages.
To migrate, update the imports:
@serwist/build.WebpackPartial
->@serwist/webpack-plugin.WebpackPartial
@serwist/build.WebpackInjectManifestOptions
->@serwist/webpack-plugin.InjectManifestOptions
@serwist/build.WebpackInjectManifestPartial
->Omit<import("@​serwist/webpack-plugin").InjectManifestOptions, keyof import("@​serwist/build").BasePartial | keyof import("@​serwist/build").InjectPartial | keyof import("@​serwist/webpack-plugin").WebpackPartial | keyof import("@​serwist/build").OptionalSwDestPartial>
@serwist/build.ViteInjectManifestOptions
->@serwist/vite.PluginOptions
With this change, validators and schemas have also been made public. Validators can be imported from "/" files, whereas schemas can be imported from "/schema" ones.
#123
4a5d51a
Thanks @DuCanhGH! - chore(next): renamed "/browser" to "/worker"This new name makes more sense than the old one, for these exports are actually for use in service workers.
To migrate, simply change all imports of
@serwist/next/browser
to those of@serwist/next/worker
:#123
4a5d51a
Thanks @DuCanhGH! - chore(peerDeps): bump minimum supported TypeScript and Node.js versionChange to your preferred way of updating Node.js
Change to your package manager
#123
7b55ac5
Thanks @DuCanhGH! - refactor(js): dropped the CommonJS buildSerwist is now an ESM-only project.
This was done because our tooling around supporting CJS had always been crappy: it was slow, had no way of supporting emitting
.d.cts
(we used to copy.d.ts
to.d.cts
), and was too error-prone (there were various issues of our builds crashing due to an ESM-only package slipping in).If you already use ESM, there's nothing to be done. Great! Otherwise, to migrate:
Migrate to ESM if possible.
Otherwise, use dynamic imports. For example, to migrate to the new
@serwist/next
:If all else fails, use
require(esm)
. This may or may not be supported on your current Node.js version.#123
7524712
Thanks @DuCanhGH! - chore(next): changeddefaultCache
's"next-data"
's handler toNetworkFirst
StaleWhileRevalidate
affectsgetServerSideProps
's freshness. See #74 for more details.#123
837cd0d
Thanks @DuCanhGH! - chore(next): renamedcacheOnFrontEndNav
tocacheOnNavigation
Generally, we avoid using abbreviations (except for acronyms) to name Serwist's APIs.
To migrate, simply replace
cacheOnFrontEndNav
withcacheOnNavigation
:Minor Changes
#123
51a686f
Thanks @DuCanhGH! - refactor(webpack,next): allow webpack to be an optionalpeerDependency
peerDependency
for@serwist/webpack-plugin
and is no longer apeerDependency
for@serwist/next
. Thanks to the fact that we currently don't use any webpack plugin, it is also not indirectly installed.#123
4a5d51a
Thanks @DuCanhGH! - feat(next): added@serwist/next/worker.PAGES_CACHE_NAME
Due to the fact that App Router pages use RSC, we define 3
runtimeCaching
entries indefaultCache
, which are"pages-rsc-prefetch"
,"pages-rsc"
, and"pages"
. This simply re-exports thesecacheName
's for the users so that they can use them in their own extensions of ourdefaultCache
.If you previously copied these values from the source code, it is recommended that you migrate to this constant:
Patch Changes
#123
db7776e
Thanks @DuCanhGH! - fix(svelte,next,vite): forcedefaultCache
to only useNetworkOnly
in development modeNetworkOnly
in development. No option to override this behaviour is provided, for it would provide little to no value. If you do need runtime caching to work during development, you have to copydefaultCache
into your code.defaultCache
, it should be placed below any custom entry, since such an entry wouldn't ever be matched otherwise.Updated dependencies [
add4fdd
,b1df273
,c65578b
,b273b8c
,6c3e789
,7b55ac5
,4a5d51a
,51a686f
,dc12dda
,7b55ac5
,e4c00af
,dc12dda
,10c3c17
,4a5d51a
]:t3-oss/t3-env (@t3-oss/env-nextjs)
v0.11.1
Compare Source
Patch Changes
2a74b72
]:v0.11.0
Compare Source
Patch Changes
8737daf
,870608d
]:v0.10.1
Compare Source
Patch Changes
#224
bed246c
Thanks @colinhacks! - refactor: add explicit return type to make lib more portableUpdated dependencies [[
bed246c
](https://redirect.github.com/t3-oss/t3-env/comConfiguration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - 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.
This PR was generated by Mend Renovate. View the repository job log.