-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update all non-major dependencies #38
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/all-minor-patch
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
January 6, 2021 23:00
7ab5da3
to
9cfb445
Compare
renovate
bot
changed the title
chore(deps): update devdependency nuxt-edge to ^2.15.0-26802759.5a5161aa
chore(deps): update all non-major dependencies
Jan 6, 2021
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
January 9, 2021 11:58
9cfb445
to
2814b9c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
January 22, 2021 17:58
2814b9c
to
25aeb64
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
January 31, 2021 08:55
25aeb64
to
3d11b66
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
8 times, most recently
from
February 15, 2021 03:29
7d04fa9
to
9ba2998
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
April 26, 2021 17:40
9ba2998
to
5961f8c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
May 9, 2021 22:36
5961f8c
to
d08e0b3
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
June 12, 2021 23:08
871bc16
to
1bb99bd
Compare
renovate
bot
changed the title
chore(deps): update all non-major dependencies
chore(deps): update dependency consola to ^2.15.3
Jun 17, 2021
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
June 17, 2021 15:20
1bb99bd
to
887c9c2
Compare
renovate
bot
changed the title
chore(deps): update dependency consola to ^2.15.3
chore(deps): update all non-major dependencies
Jun 18, 2021
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
10 times, most recently
from
June 25, 2021 01:11
4408df6
to
618a885
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 5, 2023 16:52
c77caf8
to
8ff05f6
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
September 19, 2023 04:52
e55c2b6
to
f84bf38
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
September 27, 2023 04:49
8060d3a
to
e49588c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 9, 2023 22:50
e49588c
to
c493c3e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 19, 2023 17:55
c493c3e
to
67b38cf
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
November 10, 2023 00:50
1d092f4
to
b382f7f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 21, 2023 01:33
b382f7f
to
5588332
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
December 25, 2023 18:51
5588332
to
ac7029f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
January 9, 2024 00:39
0f062cd
to
3170be8
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
January 17, 2024 15:43
f989ef4
to
784518e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
February 5, 2024 19:41
0f98949
to
fe52f88
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 7, 2024 03:40
fe52f88
to
a2c579e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
February 16, 2024 22:50
6e7f49f
to
dbae50e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 22, 2024 16:44
dbae50e
to
215b547
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 2, 2024 17:37
215b547
to
bb34220
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
March 18, 2024 21:56
30e61d2
to
7f1d11b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 20, 2024 13:17
7f1d11b
to
6fbfbd4
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
April 4, 2024 19:04
6fbfbd4
to
167bc5b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
^2.8.7
->^2.8.18
^3.0.0-rc.10
->^3.11.2
^2.3.5
->^2.9.5
^3.8.2
->^3.8.3
^4.2.2
->^4.3.1
^7.28.0
->^7.32.0
3.0.0-rc.11-27722816.abd0feb
->3.0.0-rc.9-27703329.537338f
^2.16.0-27064814.35c6ac41
->^2.16.0-27923058.4ecdc72
Release Notes
microsoft/ApplicationInsights-JS (@microsoft/applicationinsights-web)
v2.8.18
Compare Source
Changelog
What's Changed
Full Changelog: microsoft/ApplicationInsights-JS@2.8.17...2.8.18
v2.8.17
Compare Source
Changelog
What's Changed
Full Changelog: microsoft/ApplicationInsights-JS@2.8.16...2.8.17
v2.8.16
Compare Source
Changelog
2518279
: [AI] Minified CDN version has an extra "use strict" outside of the closureWhat's Changed
2518279
: [AI] Minified CDN version has an extra "use strict" outside of the closure by @MSNev in https://github.com/microsoft/ApplicationInsights-JS/pull/2151Full Changelog: microsoft/ApplicationInsights-JS@2.8.15...2.8.16
v2.8.15
Compare Source
Changelog
What's Changed
Full Changelog: microsoft/ApplicationInsights-JS@2.8.14...2.8.15
v2.8.14
Compare Source
Changelog
What's Changed
Full Changelog: microsoft/ApplicationInsights-JS@2.8.13...2.8.14
v2.8.13
Compare Source
Changelog
v2.8.12
Compare Source
Changelog
v2.8.11
Compare Source
Changelog
instrumentationKey
usage withconnectionString
1713311
: Add Policheck exclusion filev2.8.10
Compare Source
Changelog
v2.8.9
Compare Source
Changelog
v2.8.8
Compare Source
Changelog
nuxt/nuxt (@nuxt/kit)
v3.11.2
Compare Source
✅ Upgrading
As usual, our recommendation for upgrading is to run:
This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🔥 Performance
useServerHead
in dev (#26421)🩹 Fixes
navigateTo
open
option on server side (#26392)definePageMeta
in server pages (#26422)joinRelativeURL
+ share paths on server (#26407)<srcDir>/index.html
from import protection (#26430)refreshCookie
on server (22ada37b4)v-if
to wrapper in islands transform (#26386)getLatestManifest
(#26486)GlobalComponents
in multiple vue modules (#26541)transformAssetUrls
+ passhoistStatic
to vite plugin (#26563)typescript.shim
(#26607)useRoute
(#26633)💅 Refactors
navigateTo
for server (#26546)runtimeConfig
initialization of client side (#26558)📖 Documentation
prerenderRoutes
in dynamic routes (#26547)process.*
withimport.meta.*
(#26611)typescript.shim
JSDoc (#26626)🏡 Chore
❤️ Contributors
v3.11.1
Compare Source
✅ Upgrading
As usual, our recommendation for upgrading is to run:
This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🩹 Fixes
ofetch
intypescript.hoist
defaults (#26316)tsx
parser (#26314)finish
types and add to docs (0d9c63b82)undefined
name when resolving trailing slash (#26358)📖 Documentation
usePreviewMode
(#26303)useId
must be used with single root element (401370b3a)<DevOnly>
component in api section (#26029)@nuxt/schema
should be used by module authors (#26190)routeNameSplitter
example in migration docs (#25838)🏡 Chore
🤖 CI
❤️ Contributors
v3.11.0
Compare Source
👀 Highlights
This is possibly the last minor release before Nuxt v4, and so we've packed it full of features and improvements we hope will delight you! ✨
🪵 Better logging
When developing a Nuxt application and using
console.log
in your application, you may have noticed that these logs are not displayed in your browser console when refreshing the page (during server-side rendering). This can be frustrating, as it makes it difficult to debug your application. This is now a thing of the past!Now, when you have server logs associated with a request, they will be bundled up and passed to the client and displayed in your browser console. Asynchronous context is used to track and associate these logs with the request that triggered them. (#25936).
For example, this code:
will now log to your browser console when you refresh the page:
👉 We also plan to support streaming of subsequent logs to the Nuxt DevTools in future.
We've also added a
dev:ssr-logs
hook (both in Nuxt and Nitro) which is called on server and client, allowing you to handle them yourself if you want to.If you encounter any issues with this, it is possible to disable them - or prevent them from logging to your browser console.
🎨 Preview mode
A new
usePreviewMode
composable aims to make it simple to use preview mode in your Nuxt app.When preview mode is enabled, all your data fetching composables, like
useAsyncData
anduseFetch
will rerun, meaning any cached data in the payload will be bypassed.Read more in the docs.
💰 Cache-busting payloads
We now automatically cache-bust your payloads if you haven't disabled Nuxt's app manifest, meaning you shouldn't be stuck with outdated data after a deployment.
👮♂️ Middleware
routeRules
It's now possible to define middleware for page paths within the Vue app part of your application (that is, not your Nitro routes) (#25841).
⌫ New
clear
data fetching utilityNow,
useAsyncData
anduseFetch
expose aclear
utility. This is a function that can be used to setdata
to undefined, seterror
tonull
, setpending
tofalse
, setstatus
toidle
, and mark any currently pending requests as cancelled. (#26259)🕳️ New
#teleports
targetNuxt now includes a new
<div id="teleports"></div>
element in your app within your<body>
tag. It supports server-side teleports, meaning you can do this safely on the server:🚦 Loading indicator and transition controls
It's now possible to set custom timings for hiding the loading indicator, and forcing the
finish()
method if needed (#25932).There's also a new
page:view-transition:start
hook for hooking into the View Transitions API (#26045) if you have that feature enabled.🛍️ Server- and client-only pages
This release sees server- and client-only pages land in Nuxt! You can now add a
.server.vue
or.client.vue
suffix to a page to get automatic handling of it.Client-only pages will render entirely on the client-side, and skip server-rendering entirely, just as if the entire page was wrapped in
<ClientOnly>
. Use this responsibly. The flash of load on the client-side can be a bad user experience so make sure you really need to avoid server-side loading. Also consider using<ClientOnly>
with afallback
slot to render a skeleton loader (#25037).⚗️ Server-only pages are even more useful because they enable you to integrate fully-server rendered HTML within client-side navigation. They will even be prefetched when links to them are in the viewport - so you will get instantaneous loading (#24954).
🤠 Server component bonanza
When you are using server components, you can now use the
nuxt-client
attribute anywhere within your tree (#25479).You can listen to an
@error
event from server components that will be triggered if there is any issue loading the component (#25798).Finally, server-only components are now smartly enabled when you have a server-only component or a server-only page within your project or any of its layers (#26223).
🔥 Performance improvements
We've shipped a number of performance improvements, including only updating changed virtual templates (#26250), using a 'layered' prerender cache (#26104) that falls back to filesystem instead of keeping everything in memory when prerendering - and lots of other examples.
📂 Public assets handling
We have shipped a reimplementation of Vite's public asset handling, meaning that public assets in your
public/
directory or your layer directories are now resolved entirely by Nuxt (#26163), so if you have addednitro.publicAssets
directories with a custom prefix, these will now work.📦 Chunk naming
We have changed the default
_nuxt/[name].[hash].js
file name pattern for your JS chunks. Now, we default to_nuxt/[hash].js
. This is to avoid false positives by ad blockers triggering off your component or chunk names, which can be a very difficult issue to debug. (#26203)You can easily configure this to revert to previous behaviour if you wish:
💪 Type fixes
Previously users with
shamefully-hoist=false
may have encountered issues with types not being resolved or working correctly. You may also have encountered problems with excessive type instantiation.We now try to tell TypeScript about certain key types so they can be resolved even if deeply nested (#26158).
There are a whole raft of other type fixes, including some regarding import types (#26218 and #25965) and module typings (#25548).
✅ Upgrading
As usual, our recommendation for upgrading is to run:
This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🚀 Enhancements
nuxt-client
in all components (#25479)page:view-transition:start
hook (#26045)finish()
(#25932)<NuxtIsland>
can't fetch island (#25798)usePreviewMode
composable (#21705)#teleports
element for ssr teleports (#25043)typescript.hoist
(85166cced)getCachedData
(#26287)nuxtMiddleware
route rule (#25841)clear
utility touseAsyncData
/useFetch
(#26259)🔥 Performance
isPrerendered
in dev for server page (#26061)🩹 Fixes
.config/nuxt.config
(5440ecece).config/nuxt.*
(7815aa534)error
inshowError
/createError
with h3 (#25945)useId
(#25969)vueCompilerOptions
property totsConfig
(#25924)useRuntimeConfig
in Nuxt renderer (#26058)typescript.shim
in favour of volar (#26052)defu
/h3
paths in type templates (#26085)toExports
fromunimport
(#26086)AsyncDataRequestStatus
type (#26023)<html>
and<body>
attrs (#26027)node_modules
formodulesDir
(#25548)routeRules
(#26120)cookieRef
values deeply (#26151)ssrRender
(#26162)ssr: false
(f080c426a)baseUrl
within server components (#25727)useNuxtData
(#22277)publicAssetsURL
(9d08cdfd1)buildAssetsDir
(81933dfc3)joinRelativeURL
for build assets (#26282)deep
toselectiveClient
(357f8db41)consola
for now (adbd53a25)window
access more carefully (977377777)💅 Refactors
request
computation (#26191)nuxtMiddleware
toappMiddleware
(cac745470)📖 Documentation
useId
composable was introduced (#25953)domEnvironment
option to testing example (#25972)fallback
prop for<NuxtLayout>
(#26091)vue-tsc
(#26083)macros.pageMeta
andtypescript.esbuild
option (#26136)definePageMeta
page (#26139)app:manifest:update
hook (#26192)zhead
(e889a7df5)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Mend Renovate. View repository job log here.