Skip to content
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

fix(deps): update all dependencies #229

Merged
merged 1 commit into from
Jul 29, 2024
Merged

fix(deps): update all dependencies #229

merged 1 commit into from
Jul 29, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 29, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update Pending
@emotion/react (source) ^11.11.4 -> ^11.13.0 age adoption passing confidence dependencies minor
@emotion/styled (source) ^11.11.5 -> ^11.13.0 age adoption passing confidence dependencies minor
@fontsource/gabarito (source) ^5.0.4 -> ^5.0.5 age adoption passing confidence dependencies patch
@hookform/resolvers (source) ^3.6.0 -> ^3.9.0 age adoption passing confidence dependencies patch
@sentry/nextjs (source) ^8.9.2 -> ^8.20.0 age adoption passing confidence dependencies minor
@types/node (source) ^20.14.5 -> ^20.14.12 age adoption passing confidence devDependencies patch 20.14.13
eslint-config-next (source) ^14.2.4 -> ^14.2.5 age adoption passing confidence devDependencies patch
firebase (source, changelog) ^10.12.2 -> ^10.12.4 age adoption passing confidence dependencies patch
framer-motion ^11.2.11 -> ^11.3.18 age adoption passing confidence dependencies minor 11.3.19
husky ^9.0.11 -> ^9.1.3 age adoption passing confidence devDependencies minor
knip (source) ^5.21.2 -> ^5.27.0 age adoption passing confidence devDependencies minor
next (source) ^14.2.4 -> ^14.2.5 age adoption passing confidence dependencies patch
prettier (source) ^3.3.2 -> ^3.3.3 age adoption passing confidence devDependencies patch
react-hook-form (source) ^7.52.0 -> ^7.52.1 age adoption passing confidence dependencies patch
standard-version ^9.5.0 -> ^9.5.0 devDependencies replacement
typescript (source) ^5.4.5 -> ^5.5.4 age adoption passing confidence devDependencies patch
zustand ^4.5.2 -> ^4.5.4 age adoption passing confidence dependencies patch

This is a special PR that replaces standard-version with the community suggested minimal stable replacement version.


Release Notes

emotion-js/emotion (@​emotion/react)

v11.13.0

Compare Source

v11.12.0

Compare Source

getsentry/sentry-javascript (@​sentry/nextjs)

v8.20.0

Compare Source

Important Changes
  • feat(node): Allow to pass registerEsmLoaderHooks to preload (#​12998)

You can write your own custom preload script and configure this in the preload options. registerEsmLoaderHooks can be
passed as an option to preloadOpenTelemetry, which allows to exclude/include packages in the preload.

  • fix(node): Do not emit fetch spans when tracing is disabled (#​13003)

Sentry will not emit "fetch" spans if tracing is disabled. This is relevant for user who use their own sampler.

Other Changes
  • feat(feedback): Trigger button aria label configuration (#​13008)
  • feat(nestjs): Change nest sdk setup (#​12920)
  • feat(node): Extend ESM hooks options for iitm v1.10.0 (#​13016)
  • feat(node): Send client reports (#​12951)
  • feat(nuxt): Automatically add BrowserTracing (#​13005)
  • feat(nuxt): Setup source maps with vite config (#​13018)
  • feat(replay): Improve public Replay APIs (#​13000)

v8.19.0

Compare Source

node --import=@​sentry/node/import app.js


- **feat(node): Do not exit process by default when other `onUncaughtException` handlers are registered in
  `onUncaughtExceptionIntegration` (#​11532)**

In v8, we will no longer exit the node process by default if other uncaught exception handlers have been registered by
the user.

- **Better handling of transaction name for errors**

We improved the way we keep the transaction name for error events, even when spans are not sampled or performance is
disabled.

- feat(fastify): Update scope `transactionName` when handling request (#​11447)
- feat(hapi): Update scope `transactionName` when handling request (#​11448)
- feat(koa): Update scope `transactionName` when creating router span (#​11476)
- feat(sveltekit): Update scope transactionName when handling server-side request (#​11511)
- feat(nestjs): Update scope transaction name with parameterized route (#​11510)

##### Removal/Refactoring of deprecated functionality

- feat(core): Remove `getCurrentHub` from `AsyncContextStrategy` (#​11581)
- feat(core): Remove `getGlobalHub` export (#​11565)
- feat(core): Remove `Hub` class export (#​11560)
- feat(core): Remove most Hub class exports (#​11536)
- feat(nextjs): Remove webpack 4 support (#​11605)
- feat(vercel-edge): Stop using hub (#​11539)

##### Other Changes

- feat: Hoist `getCurrentHub` shim to core as `getCurrentHubShim` (#​11537)
- feat(core): Add default behaviour for `rewriteFramesIntegration` in browser (#​11535)
- feat(core): Ensure replay envelopes are sent in order when offline (#​11413)
- feat(core): Extract errors from props in unkown inputs (#​11526)
- feat(core): Update metric normalization (#​11518)
- feat(feedback): Customize feedback placeholder text color (#​11417)
- feat(feedback): Maintain v7 compat in the @​sentry-internal/feedback package (#​11461)
- feat(next): Handle existing root spans for isolation scope (#​11479)
- feat(node): Ensure tracing without performance (TWP) works (#​11564)
- feat(opentelemetry): Export `getRequestSpanData` (#​11508)
- feat(opentelemetry): Remove otel.attributes in context (#​11604)
- feat(ratelimit): Add metrics rate limit (#​11538)
- feat(remix): Skip span creation for `OPTIONS` and `HEAD` requests. (#​11149)
- feat(replay): Merge packages together & ensure bundles are built (#​11552)
- feat(tracing): Adds span envelope and datacategory (#​11534)
- fix(browser): Ensure pageload trace remains active after pageload span finished (#​11600)
- fix(browser): Ensure tracing without performance (TWP) works (#​11561)
- fix(nextjs): Fix `tunnelRoute` matching logic for hybrid cloud (#​11576)
- fix(nextjs): Remove Http integration from Next.js (#​11304)
- fix(node): Ensure isolation scope is correctly cloned for non-recording spans (#​11503)
- fix(node): Make fastify types more broad (#​11544)
- fix(node): Send ANR events without scope if event loop blocked indefinitely (#​11578)
- fix(tracing): Fixes latest route name and source not updating correctly (#​11533)
- ref(browser): Move browserTracing into browser pkg (#​11484)
- ref(feedback): Configure font size (#​11437)
- ref(feedback): Refactor Feedback types into @​sentry/types and reduce the exported surface area (#​11355)

#### 8.0.0-beta.0

This release failed to publish correctly. Use 8.0.0-beta.1 instead.

#### 8.0.0-alpha.9

This is the eighth alpha release of Sentry JavaScript SDK v8, which includes a variety of breaking changes.

Read the [in-depth migration guide](./MIGRATION.md) to find out how to address any breaking changes in your code.

##### Important Changes

- **feat: Add @​sentry-internal/browser-utils (#​11381)**

A big part of the browser-runtime specific exports of the internal `@sentry/utils` package were moved into a new package
`@sentry-internal/browser-utils`. If you imported any API from `@sentry/utils` (which is generally not recommended but
necessary for some workarounds), please check that your import statements still point to existing exports after
upgrading.

- **feat: Add loader file to node-based SDKs to support ESM monkeypatching (#​11338)**

When using ESM, it is necessary to use a "loader" to be able to instrument certain third-party packages and Node.js API.
The server-side SDKs now ship with a set of ESM loader hooks, that should be used when using ESM. Use them as follows:

```sh

v8.18.0

Compare Source

Important Changes
  • ref: Deprecate enableTracing (12897)

The enableTracing option has been deprecated and will be removed in the next major version. We recommend removing it
in favor of the tracesSampleRate and tracesSampler options. If you want to enable performance monitoring, please set
the tracesSampleRate to a sample rate of your choice, or provide a sampling function as tracesSampler option
instead. If you want to disable performance monitoring, remove the tracesSampler and tracesSampleRate options.

Other Changes
  • feat(node): Expose exclude and include options for ESM loader (#​12910)
  • feat(browser): Add user agent to INP standalone span attributes (#​12896)
  • feat(nextjs): Add experimental_captureRequestError for onRequestError hook (#​12885)
  • feat(replay): Bump rrweb to 2.25.0 (#​12478)
  • feat(tracing): Add long animation frame tracing (#​12646)
  • fix: Cleanup hooks when they are not used anymore (#​12852)
  • fix(angular): Guard ErrorEvent check in ErrorHandler to avoid throwing in Node environments (#​12892)
  • fix(inp): Ensure INP spans have correct transaction (#​12871)
  • fix(nestjs): Do not make SentryTraced() decorated functions async (#​12879)
  • fix(nextjs): Support automatic instrumentation for app directory with custom page extensions (#​12858)
  • fix(node): Ensure correct URL is passed to ignoreIncomingRequests callback (#​12929)
  • fix(otel): Do not add otel.kind: INTERNAL attribute (#​12841)
  • fix(solidstart): Set proper sentry origin for solid router integration when used in solidstart sdk (#​12919)
  • fix(sveltekit): Add Vite peer dep for proper type resolution (#​12926)
  • fix(tracing): Ensure you can pass null as parentSpan in startSpan* (#​12928)
  • ref(core): Small bundle size improvement (#​12830)

Work in this release was contributed by @​GitSquared and @​mcous. Thank you for your contributions!

Bundle size 📦

Path Size
@​sentry/browser 22.3 KB
@​sentry/browser (incl. Tracing) 33.69 KB
@​sentry/browser (incl. Tracing, Replay) 69.77 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 63.08 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 74.17 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 86.49 KB
@​sentry/browser (incl. Tracing, Replay, Feedback, metrics) 88.36 KB
@​sentry/browser (incl. metrics) 26.59 KB
@​sentry/browser (incl. Feedback) 38.98 KB
@​sentry/browser (incl. sendFeedback) 26.93 KB
@​sentry/browser (incl. FeedbackAsync) 31.54 KB
@​sentry/react 25.06 KB
@​sentry/react (incl. Tracing) 36.75 KB
@​sentry/vue 26.41 KB
@​sentry/vue (incl. Tracing) 35.57 KB
@​sentry/svelte 22.44 KB
CDN Bundle 23.52 KB
CDN Bundle (incl. Tracing) 35.47 KB
CDN Bundle (incl. Tracing, Replay) 69.87 KB
CDN Bundle (incl. Tracing, Replay, Feedback) 75.14 KB
CDN Bundle - uncompressed 69 KB
CDN Bundle (incl. Tracing) - uncompressed 104.93 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed 216.71 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 229.43 KB
@​sentry/nextjs (client) 36.61 KB
@​sentry/sveltekit (client) 34.34 KB
@​sentry/node 130.83 KB
@​sentry/node - without tracing 91.91 KB
@​sentry/aws-serverless 117.08 KB

v8.17.0

Compare Source

  • feat: Upgrade OTEL deps (#​12809)
  • fix(nuxt): Add module to build:transpile script (#​12843)
  • fix(browser): Allow SDK initialization in NW.js apps (#​12846)

v8.16.0

Compare Source

Important Changes
  • feat(nextjs): Use spans generated by Next.js for App Router (#​12729)

Previously, the @sentry/nextjs SDK automatically recorded spans in the form of transactions for each of your top-level
server components (pages, layouts, ...). This approach had a few drawbacks, the main ones being that traces didn't have
a root span, and more importantly, if you had data stream to the client, its duration was not captured because the
server component spans had finished before the data could finish streaming.

With this release, we will capture the duration of App Router requests in their entirety as a single transaction with
server component spans being descendants of that transaction. This means you will get more data that is also more
accurate. Note that this does not apply to the Edge runtime. For the Edge runtime, the SDK will emit transactions as it
has before.

Generally speaking, this change means that you will see less transactions and more spans in Sentry. You will no
longer receive server component transactions like Page Server Component (/path/to/route) (unless using the Edge
runtime), and you will instead receive transactions for your App Router SSR requests that look like
GET /path/to/route.

If you are on Sentry SaaS, this may have an effect on your quota consumption: Less transactions, more spans.

  • - feat(nestjs): Add nest cron monitoring support (#​12781)

The @sentry/nestjs SDK now includes a @SentryCron decorator that can be used to augment the native NestJS @Cron
decorator to send check-ins to Sentry before and after each cron job run:

import { Cron } from '@​nestjs/schedule';
import { SentryCron, MonitorConfig } from '@​sentry/nestjs';
import type { MonitorConfig } from '@​sentry/types';

const monitorConfig: MonitorConfig = {
  schedule: {
    type: 'crontab',
    value: '* * * * *',
  },
  checkinMargin: 2, // In minutes. Optional.
  maxRuntime: 10, // In minutes. Optional.
  timezone: 'America/Los_Angeles', // Optional.
};

export class MyCronService {
  @​Cron('* * * * *')
  @​SentryCron('my-monitor-slug', monitorConfig)
  handleCron() {
    // Your cron job logic here
  }
}
Other Changes
  • feat(node): Allow to pass instrumentation config to httpIntegration (#​12761)
  • feat(nuxt): Add server error hook (#​12796)
  • feat(nuxt): Inject sentry config with Nuxt addPluginTemplate (#​12760)
  • fix: Apply stack frame metadata before event processors (#​12799)
  • fix(feedback): Add missing h import in ScreenshotEditor (#​12784)
  • fix(node): Ensure autoSessionTracking is enabled by default (#​12790)
  • ref(feedback): Let CropCorner inherit the existing h prop (#​12814)
  • ref(otel): Ensure we never swallow args for ContextManager (#​12798)
vercel/next.js (eslint-config-next)

v14.2.5

Compare Source

firebase/firebase-js-sdk (firebase)

v10.12.4

Compare Source

For more detailed release notes, see Firebase JavaScript SDK Release Notes.

What's Changed

@​firebase/analytics@​0.10.6

Patch Changes

@​firebase/analytics-compat@​0.2.12

Patch Changes

@​firebase/app@​0.10.7

Patch Changes
  • Update SDK_VERSION.

@​firebase/app-check@​0.8.6

Patch Changes

@​firebase/app-check-compat@​0.3.13

Patch Changes

@​firebase/app-compat@​0.2.37

Patch Changes

[email protected]

Patch Changes

@​firebase/rules-unit-testing@​3.0.4

Patch Changes
framer/motion (framer-motion)

v11.3.18

Compare Source

Fixed
  • Improved correctness of AnimatePresence and made safe to use with concurrent rendering.

v11.3.17

Compare Source

Added
  • domMin feature bundle.

v11.3.16

Compare Source

Changed
  • Exporting UseScrollOptions type.

v11.3.15

Compare Source

Changed
  • Improved types for inView()'s margin property.

v11.3.14

Compare Source

Fixed
  • Wrapping usePresence's safeToRemove callback in useCallback leading to fewer re-renders.

v11.3.13

Compare Source

Fixed
  • Fixing position: fixed layout animations while scrolling.

v11.3.12

Compare Source

Fixed
  • Improving useSpring types so it accepts MotionValue<string> or MotionValue<number> but always returns MotionValue<number>.

v11.3.11

Compare Source

Fixed
  • Removing "react" import from DOM-only bundle.

v11.3.10

Compare Source

Fixed
  • Changing isBrowser check from document to window.

v11.3.9

Compare Source

Changed
  • Improve performance of window.MotionDebug check.

v11.3.8

Compare Source

Changed
  • Improve performance of layout animation calculated projection comparisons.

v11.3.7

Compare Source

Changed
  • Active render scheduling check to prevent unnecessary Set lookups.

v11.3.6

Compare Source

Changed
  • Minor performance improvements for layout animations.

v11.3.5

Compare Source

Fixed
  • Ensuring DOM bundle doesn't include react and react-dom as dependencies.

v11.3.4

Compare Source

Changed
  • Check for display: contents elements now against component props instead of Element.style.

v11.3.3

Compare Source

Changed
  • Frameloop now uses a single Set vs Set and Array, leading to smaller bundlesize and better performance under heavy load.

v11.3.2

Compare Source

Fixed
  • No longer adding background-color to will-change.

v11.3.1

Compare Source

Updated
  • Externally-provided MotionValues are no longer permanently added to will-change.

v11.3.0

Compare Source

Updated
  • Animations automatically optimised via will-change.

v11.2.14

Compare Source

Updated
  • Improved performance of core render loop.
typicode/husky (husky)

v9.1.3

Compare Source

  • fix: better handle space in PATH

v9.1.2

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

Super saiyan god dog! It's over 9.0.0!

There's a bug with this release which prevents the deprecation notice to appear and requires to remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" (which are deprecated by the way). I'll publish a new version to fix that. Sorry about any inconvenience.

What's new

You can now run package commands directly, no need for npx or equivalents.
It makes writing hooks more intuitive and is also slightly faster 🐺⚡️

### .husky/pre-commit
- npx jest
+ jest # ~0.2s faster

A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.

### .husky/pre-commit
prettier $(git diff --cached --name-only --diff-filter=ACMR | sed 's| |\\ |g') --write --ignore-unknown
git update-index --again

For more advanced use cases, see lint-staged.

Fixes

  • bunx husky init command
  • Workaround for some hooks implementation on Windows 🤷

Deprecations

  • Remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" from your hooks
  • Move your code from ~/.huskyrc to .config/husky/init.sh

Support for these will be removed in v10, notices have been added.

Friendly reminder

If Git hooks don't fit your workflow, you can disable Husky globally. Just add export HUSKY=0 to .config/husky/init.sh.

I've seen some confusion about this on X, so just a heads-up!

Sponsoring

Husky is downloaded over 45M times per month and used by ~1.5M projects. If your company wants to sponsor, you can do so here: GitHub Sponsors.

Have a nice summer ☀️ I'm open to new opportunities/consulting so feel free to drop me a message 😉

webpro-nl/knip (knip)

v5.27.0

Compare Source

v5.26.0

Compare Source

v5.25.2

Compare Source

  • Include additional workspaces when loading manifests (resolves #​722) (ca03fd8)
  • Move & refactor setRefs → findInternalReferences (deeb2ac)
  • Minor refactors (09fc536)
  • Always pre-set moduleResolution: bundler if tsconfig.json (3c13118)
  • No need to publish twice here (34be850)
  • Minor refactors (c1db1ec)
  • Update docs re. shared/isolated workspaces (699fd28)
  • Set moduleResolution: bundler if not set and don't share it (resolves #​719) (2c24678)
  • fix: Use parseFragment instead of text node which breaks formatting (#​720) (3201c07)

v5.25.1

Compare Source

v5.25.0

Compare Source

v5.24.4

Compare Source

  • Start using central resolveEntry from plugin helpers (#​716) (65d8098)

v5.24.3

Compare Source

  • Improve Angular plugin a bit + add fixture/test (#​717) (641b5fc)
  • Fix Cannot read properties of undefined (reading 'name') (#​718) (f0f9f5a)

v5.24.2

Compare Source

vercel/next.js (next)

v14.2.5

Compare Source

prettier/prettier (prettier)

v3.3.3

Compare Source

diff

Add parentheses for nullish coalescing in ternary (#​16391 by @​cdignam-segment)

This change adds clarity to operator precedence.

// Input
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.2
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.3
foo ? (bar ?? foo) : baz;
(foo ?? bar) ? a : b;
a ? b : (foo ?? bar);
Add parentheses for decorator expressions (#​16458 by @​y-schneider)

Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.

// Input
@&#8203;(foo`tagged template`)
class X {}

// Prettier 3.3.2
@&#8203;foo`tagged template`
class X {}

// Prettier 3.3.3
@&#8203;(foo`tagged template`)
class X {}
Support @let declaration syntax (#​16474 by @​sosukesuzuki)

Adds support for Angular v18 @let declaration syntax.

Please see the following code example. The @let declaration allows you to define local variables within the template:

@&#8203;let name = 'Frodo';

<h1>Dashboard for {{name}}</h1>
Hello, {{name}}

For more details, please refer to the excellent blog post by the Angular Team: Introducing @​let in Angular.

We also appreciate the Angular Team for kindly answering our questions to implement this feature.

Microsoft/TypeScript (typescript)

v5.5.4

Compare Source


Configuration

📅 Schedule: Branch creation - "before 1am on Monday" in timezone Asia/Jakarta, 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

vercel bot commented Jul 29, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
spoker ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 29, 2024 4:26am

Copy link

sonarcloud bot commented Jul 29, 2024

@sozonome sozonome merged commit 3985523 into dev Jul 29, 2024
6 checks passed
@sozonome sozonome deleted the renovate/all branch July 29, 2024 04:44
sozonome added a commit that referenced this pull request Aug 1, 2024
fix(deps): update all dependencies (#229)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant