chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@next/font	13.4.3 -> 13.4.4
@prisma/client (source)	^4.14.1 -> ^4.15.0
cron	^2.3.0 -> ^2.3.1
dotenv	^16.0.3 -> ^16.1.3
formik (source)	^2.2.9 -> ^2.4.1
framer-motion	^10.12.12 -> ^10.12.16
next (source)	^13.4.3 -> ^13.4.4
winston	^3.8.2 -> ^3.9.0
yup	^1.1.1 -> ^1.2.0

---

Release Notes

vercel/next.js

v13.4.4

Compare Source

Core Changes

• test(turbopack): script to sync latest test lists: #​50008
• Pages Module Transition: #​49962
• Server Actions: Fix member expr in closure captured values: #​50020
• Error in next export when serverActions is enabled: #​50039
• [turbopack]: Update renamed SubpathValue: #​49636
• Fix default metadata is missing in root not-found: #​50044
• Always defer close tags to be the suffix of body stream: #​50056
• Fix types of cookies(): #​50052
• Fix client references extraction of CJS exports analysis: #​50059
• Add x-forwarded-* headers to turbopack renders: #​50012
• Remove node-sass from peerDependencies: #​50065
• Add optional generic parameter to NextResponse: #​47526
• feat(turbopack): initial sass-loader support: #​49882
• update test snapshots: #​50159
• [create-next-app]: respecting the user's init.defaultBranch git con…: #​49960
• Update swc_core to v0.76.18: #​50137
• Fix navigating on not-found: #​50047
• Fix env variables set in next.config.js: #​50179
• Add warning for edge with force-static: #​50182
• fix: add missing draftMode type to GetServerSidePropsContext: #​50184
• Fix react fetch deduping without next cache: #​50187
• Fix pages react alias: #​50128
• Add the node condition to import resolution: #​50007
• test(turbopack): run next.js integration tests with denylist: #​50172
• Move debugging variable into useEffect: #​50210
• refactor webpack loaders: #​49535
• Fix static workers distributing: #​50194
• Ensure NEXT_DYNAMIC_NO_SSR_CODE has a unique name: #​50219
• fix: Added blockfrost-js, lucid-cardano & mongoose package to srvExtPackages to prevent issue #​49783 from happening.: #​49938
• change static path to /_next/static/media: #​50207
• Add special route types to the link type declaration: #​50066
• fix: NODE_OPTIONS='--inspect' in next dev for debugging: #​48019
• enable more test cases for turbopack: #​50154
• feat(next-swc): Implement CJS optimizer: #​49972
• Fix alias for react-dom/server: #​50238
• Revert "feat(next-swc): Implement CJS optimizer": #​50247
• Fix free port handling: #​50248
• feat(next-swc): Add CJS optimizer again: #​50249
• Fix edge case in the CJS optimizer: #​50258
• Remove static analysis of process.env: #​50260
• Update next start listening to behave consistently: #​50293
• Update server invoke-request: #​50296
• Update unstable_cache key to include args: #​50301
• Add root detection utils: #​50305
• fix sass handling after refactoring: #​50259
• Alias next/server for edge runtime: #​50268
• [turbopack]: Serve _devMiddlewareManifest.json from router: #​50241
• Fix catch-all edge app route: #​50313
• land: Include charset=utf-8 with x-component Content-Type header: #​50314
• do not apply sass loader on existing loaders: #​50308
• Add missing react-dom/client alias: #​50324
• Fix missing error when using Actions on the client layer without enabling the feature flag: #​50257
• remove allowlist, only use denylist, enable newly passing tests: #​50325
• Fix SWC loader options for files outside of RSC layers: #​50341

Documentation Changes

• Update app-static-to-dynamic-error.md: #​50085
• Update invalid-new-link-with-extra-anchor.md: #​50036

Example Changes

• fix: use node copyFile for cross-platform support: #​48740
• Clerk example updates: #​50021
• Fix TypeScript error in with-mongodb example: #​50094
• Use correct casing in filenames: #​50223

Misc Changes

• test: disable cache flaky test: #​50064
• add tracing for turbopack: #​49920
• ci: update github token: #​50216
• Fix metadata e2e deploy test: #​50252
• Fix middleware e2e deploy test: #​50317
• Parallelize Turbopack CI tests: #​50292
• makeDir should use func: #​50136

Credits

Huge thanks to @​kwonoj, @​wyattjoh, @​shuding, @​huozhi, @​jridgewell, @​ijjk, @​karlhorky, @​lycuid, @​MarkAtOmniux, @​darshkpatel, @​johnta0, @​kdy1, @​sokra, @​timneutkens, @​devagrawal09, @​ibrahemid, @​styfle, @​JesseKoldewijn, @​padmaia, @​Cow258, @​javivelasco, and @​05lazy for helping!

prisma/prisma

v4.15.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

For this release, we focused on fixing bugs and making smaller quality-of-life improvements.

Support for custom arguments for prisma db seed

This release adds support for defining and passing arbitrary arguments to prisma db seed. This creates the opportunity for you to define your own arguments in your seed file that you could pass to the prisma db seed command. A few example use-cases include, but are not limited to:

• Seeding different data in different environments
• Partially seeding data in some tables

Here is an example seed.ts file that defines custom arguments for seeding different data in different environments:

// prisma/seed.ts
import { parseArgs } from "node:util";

const options = {
  environment: { type: 'string', },
}

async function main() {
  const { values: { environment } } = parseArgs({ options })
  
  switch (environment) {
    case "development":
      /** do something for development */
      break;
    case "test":
      /** do something  for test  environment */
      break;
    default:
      break;
  }
}

main()

You can then provide the environment argument when executing the seed script as follows:

npx prisma db seed -- --environment development

Let us know what you think, share example usage of this feature, and create a bug report if you run into any issues.

Improved error messages when Query Engine file is not found

This release improves the error messages returned by Prisma Client when the Query Engine file is not found. A few reasons the Query Engine file might be missing from your application bundle include when:

• The downloaded Query Engine doesn’t match the runtime/ target platform your application is running on.
• The Query Engine is not copied to your final application bundle during the build step.

We hope these error messages are helpful while debugging your application.

Prisma VS Code extension improvements

In this release, we made a few improvements to our VS Code extension:

1. Updated the file system watcher that is responsible for restarting the TypeScript server when prisma generate is run to ensure the types are in sync

   Note:

   • This new approach is currently only available on Windows and Linux. We plan on adding support for the new file system watcher on macOS soon.
   • This requires both Prisma CLI & VS code extension version 4.15.0 or higher

2. Added Quick Fixes action for unique identifiers for MongoDB to add the @map("_id") attribute function when it’s missing on an identifier field

   Screen.Recording.2023-05-17.at.19.22.20.mov

3. Support for renaming symbols for composite types and views

   type-symbol-rename.mov

Fixes and improvements

Prisma Client

• Prisma generate - Error: write EPIPE on WSL <-> Windows
• prisma generate is blocked by query-engine-rhel-openssl-1.0.x opening in Notepad on Windows
• Generated client output path hardcoded to build environment
• Issue with Yarn Workspace Monorepo: Query engine binary for current platform could not be found.
• Cloning a project with checked in node_modules (from another platform) leads to platform engine not being present
• SvelteKit, Vite and Prisma "module not defined"
• Schema File Not Found in non monorepo with custom output
• Deploying to Cloudflare Workers | "PrismaClient is unable to be run in the browser"
• Inline/bundle the contents of the prisma schema on generate
• Netlify: Query engine library for current platform "rhel-openssl-1.0.x" could not be found. You incorrectly pinned it to rhel-openssl-1.0.x
• Query Engine Library Not Found
• No client schema when using PrismaClient during cached (standard) Netlify build
• Module "@​prisma/client" has no exported member "PrismaClient"
• EPERM: operation not permitted
• prisma/client crashes when used with older versions of react-refresh
• Unable to run prisma cli in pnpm monorepo from workspace install
• Misleading error message when the query engine is not found
• When setting custom client output directory, generated package.json does not include "sideEffects: false"
• You already added the platform "debian-openssl-1.1.x" to the "generator" block in the "schema.prisma" file as described in https://pris.ly/d/client-generator, but something went wrong.
• Prisma seems to be looking in the wrong location for rhel-openssl-1.0.x
• Can't find prisma engine
• Cannot find name '$PrismaModel' due to feature extendedWhereUnique with preview feature fieldReference
• Netlify build fails with PrismaClientInitializationError
• i'm getting the error while requesting the api
• Query engine library for current platform could not be found.
• Prisma unable to reconnect if initial connection fails
• GraphQL protocol encoder incorrectly turns empty array into empty object.
• GraphQL protocol: Invalid Date values silently turn into nulls
• @​prisma/client/edge + Cloudflare Worker / wrangler = Could not resolve "os"
• Client is bricked from connecting to DB if first attempt fails.
• JSON protocol: incorrect recursive composites detection through multiple nesting levels
• fieldReference is not working with enums

Prisma Migrate

• Pass extra arguments to prisma db seed to the seed command
• Typo in generating migration SQL to add enum.

Language tools (e.g. VS Code)

• MongoDB: Quick fix for missing @map("_id") annotation
• Rename composite types
• Views: Support for rename
• TextDocument deprecation
• Lib name change vsce -> @​vscode/vsce

Credits

Huge thanks to @​RobertCraigie, @​KhooHaoYit, @​art049, @​luxaritas, @​mrazauskas, @​maxmartynov, @​haneenmahd for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, June 1 at 5 pm Berlin | 8 am San Francisco.

kelektiv/node-cron

v2.3.1

Compare Source

Added

• Logo!
• New test cases

Fixed

• Linting issues

motdotla/dotenv

v16.1.3

Compare Source

Removed

• Removed browser keys for path, os, and crypto in package.json. These were set to false incorrectly as of 16.1. Instead, if using dotenv on the front-end make sure to include polyfills for path, os, and crypto. node-polyfill-webpack-plugin provides these.

v16.1.2

Compare Source

Changed

• Exposed private function _configDotenv as configDotenv. #​744

v16.1.1

Compare Source

Added

• Added type definition for decrypt function

Changed

• Fixed {crypto: false} in packageJson.browser

v16.1.0

Compare Source

Added

• Add populate convenience method #​733
• Accept URL as path option #​720
• Add dotenv to npm fund command
• Spanish language README #​698
• Add .env.vault support. 🎉 (#​730)

ℹ️ .env.vault extends the .env file format standard with a localized encrypted vault file. Package it securely with your production code deploys. It's cloud agnostic so that you can deploy your secrets anywhere – without risky third-party integrations. read more

Changed

• Fixed "cannot resolve 'fs'" error on tools like Replit #​693

formium/formik

v2.4.1

Compare Source

Patch Changes

• 2b194c2 #​3808 Thanks @​NagaiKoki! - fix type of setFieldValue function

• 708bcb2 #​3813 Thanks @​probablyup! - Revert FieldArray "shouldComponentUpdate" performance optimization. As it turns out, it's a common use case to have JSX controlled via non-Formik state/props inside of FieldArray, so it's not safe to cancel re-renders here.

• 187e47d #​3815 Thanks @​probablyup! - Revert Yup transform support for the time being, this may be re-introduced in a future release under an opt-in prop.

v2.4.0

Compare Source

Minor Changes

• 2f53b70 #​3796 Thanks @​probablyup! - Add support for Yup "transforms".

v2.3.3

Compare Source

Patch Changes

• f075a0c #​3798 Thanks @​probablyup! - Fixed the use of generics for the ArrayHelpers type such that any[] is the default array type and for each individual method the array item type can be overridden if necessary.

v2.3.2

Compare Source

Patch Changes

• f086b5a #​3237 Thanks @​pieplu! - Changed getIn to return undefined when it can't find a value AND a parent of that value is "falsy" ( "" / 0 / null / false )

• 6d8f018 #​3792 Thanks @​probablyup! - Update the type for setFieldValue to reflect the returned Promise and potential returned error(s).

v2.3.0

Compare Source

Minor Changes

• 73de78d #​3788 Thanks @​probablyup! - Added typescript generics to ArrayHelpers interface and its methods so that users who use TypeScript can set the type for their arrays and have type safety on array utils. I have also gone ahead and made supplying a type for the generic optional for the sake of backwards compatibility so any existing TS code that does not give a type for the FieldArray will continue to work as they always have.

• 39a7bf7 #​3786 Thanks @​probablyup! - Yup by default only allows for cross-field validation within the
  same field object. This is not that useful in most scenarios because
  a sufficiently-complex form will have several yup.object() in the
  schema.

  const deepNestedSchema = Yup.object({
    object: Yup.object({
      nestedField: Yup.number().required(),
    }),
    object2: Yup.object({
      // this doesn't work because `object.nestedField` is outside of `object2`
      nestedFieldWithRef: Yup.number()
        .min(0)
        .max(Yup.ref('object.nestedField')),
    }),
  });

  However, Yup offers something called context which can operate across
  the entire schema when using a \$ prefix:

  const deepNestedSchema = Yup.object({
    object: Yup.object({
      nestedField: Yup.number().required(),
    }),
    object2: Yup.object({
      // this works because of the "context" feature, enabled by $ prefix
      nestedFieldWithRef: Yup.number()
        .min(0)
        .max(Yup.ref('$object.nestedField')),
    }),
  });

  With this change, you may now validate against any field in the entire schema,
  regardless of position when using the \$ prefix.

v2.2.10

Compare Source

Patch Changes

• 22e236e #​3784 Thanks @​probablyup! - Improve performance of the FieldArray component by adding a shouldComponentUpdate check; this should help avoid unnecessary re-renders which may affect the performance of a form.

• bc9cb28 #​3785 Thanks @​probablyup! - Fixed field error state for array fields that have an error and become empty through an API like arrayHelpers.remove.

  The prior behavior resolved the field error to [undefined], now it is simply undefined.

• 9cbf150 #​3787 Thanks @​probablyup! - Fix infinite loop issue in Field when field helpers (setTouched, etc) are used as an argument in React.useEffect.

• 9c75a9f #​3780 Thanks @​probablyup! - Fixed an issue with array field errors being incorrectly split into an array of individual characters instead of an array of error strings.

• 35fa4cc #​3783 Thanks @​probablyup! - Fix validation of deep.dot.path field references when using the validateField API.

framer/motion

v10.12.16

Compare Source

Fixed

• Fixing unit conversion when animating translateX/translateY.

v10.12.15

Compare Source

Fixed

• Fixed timing bug when mixing layout prop and animate().
• Removing errant log from resolveConstraints.

v10.12.14

Compare Source

Fixed

• Ensure new layout components animate correctly on the first re-render.

v10.12.13

Compare Source

Fixed

• Fixed scale correction in elements that have finished layout animations.

winstonjs/winston

v3.9.0

Compare Source

Functionality changes

• Handle undefined errors in getAllInfo in exception-handler in https://github.com/winstonjs/winston/pull/2208; thanks to new contributor @​eivindrs
• fix: properly allow passing non-array transport in https://github.com/winstonjs/winston/pull/2256; thanks to new contributor @​Tanuel
• fix #​1732 (Http Transport uses JSON format options as request options) in https://github.com/winstonjs/winston/pull/2272; thanks to new contributor @​MoritzLoewenstein (minor version bump per comment on the issue)
• fix: add guard clause to prevent FD leak in https://github.com/winstonjs/winston/pull/2301; thanks to new contributor @​td-tomasz-joniec

Dependency updates by @​dependabot + CI autotesting

• Bump eslint from 8.23.0 to 8.32.0 by @​dependabot in https://github.com/winstonjs/winston/pull/2209, https://github.com/winstonjs/winston/pull/2236, https://github.com/winstonjs/winston/pull/2258, & https://github.com/winstonjs/winston/pull/2271
• Bump @​babel/core from 7.19.0 to 7.20.12 by @​dependabot in https://github.com/winstonjs/winston/pull/2206, https://github.com/winstonjs/winston/pull/2234, https://github.com/winstonjs/winston/pull/2259, & https://github.com/winstonjs/winston/pull/2275
• Bump @​types/node from 18.0.0 to 18.11.18 by @​dependabot in https://github.com/winstonjs/winston/pull/2215, https://github.com/winstonjs/winston/pull/2235, & https://github.com/winstonjs/winston/pull/2264
• Bump @​babel/preset-env from 7.19.0 to 7.20.2 by @​dependabot in https://github.com/winstonjs/winston/pull/2218 & https://github.com/winstonjs/winston/pull/2244
• Bump safe-stable-stringify from 2.3.1 to 2.4.3 by @​dependabot in https://github.com/winstonjs/winston/pull/2217 & https://github.com/winstonjs/winston/pull/2292
• Bump @​babel/cli from 7.18.10 to 7.19.3 by @​dependabot in https://github.com/winstonjs/winston/pull/2216
• Bump json5 from 2.2.1 to 2.2.3 by @​dependabot in https://github.com/winstonjs/winston/pull/2260

Documentation changes

• Fix readme typo in https://github.com/winstonjs/winston/pull/2230; thanks to new contributor @​aretecode
• create new example for ready to use in https://github.com/winstonjs/winston/pull/2240; thanks to new contributor @​myagizmaktav
• minor fixes to publishing.md

Build Infrastructure changes

• GitHub Workflows security hardening in https://github.com/winstonjs/winston/pull/2252; thanks to new contributor @​sashashura

jquense/yup

v1.2.0

Compare Source

Features

• expose printValue (#​2002) (#​2008) (1fadba1)
• pass options to default(options => value) (e5c5440), closes #​1984

1.1.1 (2023-04-14)

Bug Fixes

• docs: Broken anchores (#​1979) (4ed4576)
• make null validation errors consistent across schema (#​1982) (f999497)
• object: excluded edges are merged when concating schema (c07b08f), closes #​1969

---

Configuration

📅 Schedule: Branch creation - "before 12pm on Sunday" (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.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.