Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
N
next.js
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Alex
next.js
Commits
53b1924b
Unverified
Commit
53b1924b
authored
Jan 26, 2024
by
Delba de Oliveira
Committed by
GitHub
Jan 26, 2024
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Docs: Add note about `revalidatePath` invalidating router cache (#61142)
parent
76641dae
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
0 deletions
+2
-0
revalidatePath.mdx
docs/02-app/02-api-reference/04-functions/revalidatePath.mdx
+2
-0
No files found.
docs/02-app/02-api-reference/04-functions/revalidatePath.mdx
View file @
53b1924b
...
@@ -9,6 +9,8 @@ description: API Reference for the revalidatePath function.
...
@@ -9,6 +9,8 @@ description: API Reference for the revalidatePath function.
>
>
>
-
`revalidatePath`
is
available
in
both
[
Node
.
js
and
Edge
runtimes
](
/
docs
/
app
/
building
-
your
-
application
/
rendering
/
edge
-
and
-
nodejs
-
runtimes
)
.
>
-
`revalidatePath`
is
available
in
both
[
Node
.
js
and
Edge
runtimes
](
/
docs
/
app
/
building
-
your
-
application
/
rendering
/
edge
-
and
-
nodejs
-
runtimes
)
.
>
-
`revalidatePath`
only
invalidates
the
cache
when
the
included
path
is
next
visited
.
This
means
calling
`revalidatePath`
with
a
dynamic
route
segment
will
not
immediately
trigger
many
revalidations
at
once
.
The
invalidation
only
happens
when
the
path
is
next
visited
.
>
-
`revalidatePath`
only
invalidates
the
cache
when
the
included
path
is
next
visited
.
This
means
calling
`revalidatePath`
with
a
dynamic
route
segment
will
not
immediately
trigger
many
revalidations
at
once
.
The
invalidation
only
happens
when
the
path
is
next
visited
.
>
-
Currently
,
`revalidatePath`
invalidates
all
the
routes
in
the
[
client
-
side
Router
Cache
](
/
docs
/
app
/
building
-
your
-
application
/
caching
#router-cache). This behavior is temporary and will be updated in the future to apply only to the specific path.
>
-
Using
`revalidatePath`
invalidates
**
only
the
specific
path
**
in
the
[
server
-
side
Route
Cache
](
/
docs
/
app
/
building
-
your
-
application
/
caching
#full-route-cache).
## Parameters
## Parameters
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment