ci(changesets): next version packages #3154
Merged
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.
Releases
@pankod/[email protected]
Major Changes
#3140
102bfbf3283
Thanks @aliemir! - - Bumped Next.js to 13appDir
option innext.config.js
to allow for the latest Next.js features.pages
directoryCurrent support for
pages
directory has not changed and will continue to work as before. It will be supported as long asNext.js
continues to support and prompts it as the stable way of working withNext.js
.appDir
optionappDir
option is a new experimental feature inNext.js
that introduces a bunch of new features. It is currently in beta and is not stable. It is not recommended to use it in production. But can be used alongside the currentpages
directory support.To use
appDir
option, you need to add it to yournext.config.js
file.Using
appDir
with refineWe've needed to make some changes to the
@pankod/refine-nextjs-router
to make it work with the current structure of theapp
directory feature. To make sure these do not break the current support forpages
directory, we've added a new exports at the sub path@pankod/refine-nextjs-router/app
that can be used with theappDir
option.Note
To make optional catch-all routes to work with the
app
directory, you need to define them as directories unlike the option of defining them as files withpages
directory.You need to use
NextRouteComponent
from@pankod/refine-nextjs-router/app
instead ofNextRouteComponent
from@pankod/refine-nextjs-router
when usingappDir
option.Inside your
layout
file, you need to bindparams
torouterProvider
to make sure@pankod/refine-nextjs-router
can work properly with the new structure.Warning
Please note that, unlike the
routerProvider
from the@pankod/refine-nextjs-router
,routerProvider
from@pankod/refine-nextjs-router/app
is a function and you need to bindparams
to make it work properly.Warning
You need to add
"use client";
directive to bothlayout.tsx
andpage.tsx
insideapp/[[...refine]]
directory.Warning
checkAuthentication
does not work withappDir
. We're aiming to release a substitute for it using middleware but for now its not included in this release.@pankod/[email protected]
Minor Changes
15d3fd535a2
Thanks @yildirayunlu! - Update compiler option on targetes6
for@pankod/refine-sdk
.@pankod/[email protected]
Patch Changes
15d3fd535a2
]: