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

chore(deps): update all non-major dependencies #296

Merged
merged 1 commit into from
Mar 5, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 5, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@next/font ^13.2.1 -> ^13.2.3 age adoption passing confidence
@next/font 13.2.1 -> 13.2.3 age adoption passing confidence
@prisma/client (source) ^4.10.1 -> ^4.11.0 age adoption passing confidence
@types/node (source) 18.14.1 -> 18.14.6 age adoption passing confidence
@typescript-eslint/eslint-plugin ^5.53.0 -> ^5.54.0 age adoption passing confidence
@typescript-eslint/parser ^5.53.0 -> ^5.54.0 age adoption passing confidence
eslint (source) 8.34.0 -> 8.35.0 age adoption passing confidence
eslint-config-next 13.2.1 -> 13.2.3 age adoption passing confidence
framer-motion ^10.0.0 -> ^10.0.1 age adoption passing confidence
next (source) ^13.2.1 -> ^13.2.3 age adoption passing confidence
prisma (source) ^4.10.1 -> ^4.11.0 age adoption passing confidence
turbo (source) ^1.8.2 -> ^1.8.3 age adoption passing confidence
yup ^1.0.1 -> ^1.0.2 age adoption passing confidence

Release Notes

vercel/next.js

v13.2.3

Compare Source

Core Changes
  • build(cargo): update turbopack: #​46581
  • Fix(typedRoutes): fixed Webpack crashing without redirects/rewrites: #​46591
  • Fix async generateMetadata type in ts plugin: #​46596
  • Async Storage Cleanup: #​46586
  • Ensure URL can be passed to fetch correctly #​46592
  • Fix static to dynamic error in dev: #​46597
  • Add page path to repeated slashes in href error: #​46557
  • Implement middleware support for Turbopack: #​46397
Credits

Huge thanks to @​jridgewell, @​DuCanhGH, @​wyattjoh, and @​hanneslund for helping!

v13.2.2

Compare Source

Core Changes
  • fix(ts): correctly augment next when typedRoutes: true: #​46332
  • feat(cssnano-simple): merge into next repo: #​46380
  • Dedupe next/font preload tags: #​46354
  • Print command for current packet manager in @​next/font warning: #​46359
  • Loader refactoring: #​46304
  • Support server-only inside pages/api: #​46328
  • fix: improve next.config.js validation for images prop: #​46326
  • Revert "Support server-only inside pages/api": #​46388
  • Add relative app dir field: #​46393
  • test(integration): properly pipe turbopack binary stdouts: #​46382
  • chore: improve error when exporting metadata from client component: #​46334
  • Update server reference syntax and tests: #​46389
  • Fix SWC error wrongly formatted : #​46412
  • Fix(typedRoutes): replaced readFile + replaceAll, hid utils types, fixed duplication in type Route, fixed route groups on Windows: #​46378
  • Ensure fetch fields are detected with RequestInit: #​46398
  • Ensure SERVER_REFERENCE_MANIFEST is included in output files: #​46420
  • Fix duplicate link type asset generation: #​46421
  • chore: show large data warning once per page on prod: #​46323
  • fixed spelling mistake: #​46446
  • Fix(typedRoutes): export createServer from 'next/types/index.d.ts': #​46462
  • chore: Loss of precision due to Date now amplification: #​46344
  • Fix next/font/google config not being used: #​46484
  • Add @​latest to next/font codemod warning: #​46486
  • Add error for styled-jsx in Server Component: #​46482
  • Refactor style loader code: #​46490
  • Fix SWC's auto_cjs handling: #​46448
  • Add theme color media support for metadata: #​46502
  • Fix(typedRoutes): fixed 'next' imports on TS < 5.0: #​46507
  • fix: codemod should preserve type only import: #​46512
  • Add interactive-widget optional property to Viewport type: #​46506
  • Update router filter to be less sensitive: #​46515
  • Update fetch cache internal handling: #​46522
  • Upgrade precompiled react packages: #​46365
  • fix(error-overlay): hide "Learn more" when up-to-date: #​46488
  • Refactor route types to include rewrites and redirects: #​46327
  • Added bcrypt to the serverComponentsExternalPackages auto-optOut list: #​46532
  • feat: add support for the src folder for the instrumentation hook: #​46529
  • Fix viewport typing and refactor constants: #​46569
  • Fix shared entries/invalidators module scope: #​46533
  • Fix CSS imports not included in entries with a custom extension: #​46571
  • fix: should not warn when image unmounts: #​46567
  • fix: generate next-env.d.ts file during next lint command: #​46249
  • Fix infinite invalidations loop in app dir (#​46526)
  • Use og:image instead of og:image:url: #​46570
  • Fix usage of textDecoder to not break utf8 characters: #​46564
  • Fix app client child entry not being disposed when deleting the file: #​46583
  • Fix: canonical should allow relative urls: #​46584
Documentation Changes
Example Changes
Misc Changes
  • test(next-script): teardown next-dev instance via jest hooks: #​46383
  • Apply filtering after rewrite as well (#​46390
  • Fix fetch cache key inputs and encoding (#​46392
  • Fix failing app-static deploy test: #​46395
  • Cover 1st-party examples with tests (#​45270)Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@​users.noreply.github.com> Co-authored-by: Tim Neutkens tim@timneutkens.nl
  • Updates cms-sanity example to use Sanity v3 (#​45662
  • Support Two-letter Language Codes(ISO-639-1) to metadata HrefLang types (#​46285
  • [next/codemod]: Preserve type-only imports when using next-image-to-legacy-image (#​46460
  • Remove incorrect comment (#​46467)Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@​users.noreply.github.com>
  • dynamic = "error" violations should be shown in error overlay (#​45893
  • Fix typo from next-font (#​46468
  • Add image generation test to app route: #​46449
  • Remove baseUrl from create-next-app ts/jsconfig.json: #​46458
  • Update fetch cache key (#​46513
Credits

Huge thanks to @​balazsorban44, @​delbaoliveira, @​SukkaW, @​ijjk, @​hanneslund, @​JanKaifer, @​GitRowin, @​shuding, @​styfle, @​mjunix, @​kwonoj, @​thiskevinwang, @​DuCanhGH, @​SethFalco, @​yun-jay, @​harrytothemoon, @​timneutkens, @​huozhi, @​thomasballinger, @​aretrace, @​JesseKoldewijn, @​feedthejim, @​serkanbektas, @​teobler, and @​vadzim for helping!

prisma/prisma

v4.11.0

Compare Source

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

Highlights
JSON protocol Early Preview

This release introduces an early Preview feature: JSON protocol.

During performance investigations and optimizations, though, we noticed that the existing implementation added a CPU and memory overhead that was especially noticeable for larger Prisma schemas. Therefore, we found an alternative way to express our queries without needing that overhead: JSON.

To try out the new protocol, enable the jsonProtocol Preview feature in your Prisma schema:

generator client {
  provider        = "prisma-client-js"  
  previewFeatures = ["jsonProtocol"]
}

Regenerate Prisma Client to use the new JSON protocol.

For environments or situations where it is not viable to enable the Preview feature flag to your Prisma schema file, we also added an environment variable that you can use to force the use of the JSON Protocol Preview feature: PRISMA_ENGINE_PROTOCOL=json.

Note: This is an early Preview feature with a significant limitation: Invalid input to Prisma Client will throw unpolished, internal errors that are less descriptive and user-friendly than our usual ones. We intend to improve these future releases. Using it with Data Proxy and Prisma Data Platform currently also leads to errors.

We expect using jsonProtocol to improve Prisma Client's startup performance significantly. This will likely have a more significant impact on applications with larger Prisma schemas.

We would appreciate your feedback on this feature on the following particularly:

  1. Does using this preview feature introduce any regressions or problems in your application?
  2. If not, how does it influence the performance of your application? Can you share before and after measurements?

For feedback, please comment on the GitHub feedback issue.

Introspection support for MySQL, SQL Server, and CockroachDB views

You can now run prisma db pull against your database to populate your Prisma schema with your views in MySQL, SQL Server, and CockroachDB.

To learn more, refer to our documentation on views introspection. Try it out and let us know your thoughts in this GitHub issue.

Prisma Client extensions improvements: raw query operations

This release adds support for extending top-level raw query operations.

const xprisma = prisma.$extends({
  query: {
    // relational databases
    $queryRaw({ args, query, operation }) {
      // handle $queryRaw operation
      return query(args)
    },
    $executeRaw({ args, query, operation }) {
      // handle $executeRaw operation
      return query(args)
    },
    $queryRawUnsafe({ args, query, operation }) {
      // handle $queryRawUnsafe operation
      return query(args)
    },
    $executeRawUnsafe({ args, query, operation }) {
      // handle $executeRawUnsafe operation
      return query(args)
    },
    // MongoDB
    $runCommandRaw({ args, query, operation }) {
      // handle $runCommandRaw operation
      return query(args)
    },
  },
})
Webpack plugin for Next.js apps using Prisma in monorepo setups

If you've been using Prisma Client in a Next.js app in a monorepo setup, you might have seen this infamous error message:

Error: ENOENT: no such file or directory, open schema.prisma

We finally pinpointed the problem's source to the Next.js bundling step and opened an issue in the Next.js repository for Vercel to investigate and hopefully fix it.

In the meantime, we've created a workaround via a webpack plugin that makes sure your Prisma schema is copied to the correct location: @prisma/nextjs-monorepo-workaround-plugin.

To use the plugin, first install it:

npm install -D @&#8203;prisma/nextjs-monorepo-workaround-plugin

Import the plugin into your next.config.js file and use it in config.plugins:

const { PrismaPlugin } = require('@&#8203;prisma/nextjs-monorepo-workaround-plugin')
module.exports = {
  webpack: (config, { isServer }) => {
    if (isServer) {
      config.plugins = [...config.plugins, new PrismaPlugin()]
    }
    return config
  },
}

For further information, refer to our documentation to learn how to use it and open an issue if it doesn't work as expected.

Fixes and improvements
Prisma Client
Prisma Migrate
Credits

Huge thanks to @​KhooHaoYit, @​rintaun, @​ivan, @​Mini256, @​Lioness100, @​yukukotani, @​sandrewTx08, @​fubhy, @​zachtil, @​unflxw, @​Mosaab-Emam 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, March 2 at 5 pm Berlin | 8 am San Francisco.

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.54.0

Compare Source

Features
  • eslint-plugin: [promise-function-async] check for promises in implicit return types (#​6330) (de1e5ce), closes #​6329
typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.54.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

eslint/eslint

v8.35.0

Compare Source

Features

  • 8e34a04 feat: add afterHashbangComment option to lines-around-comment rule (#​16920) (SUZUKI Sosuke)
  • c8c0c71 feat: Move all and recommended configs into package. (#​16844) (Nicholas C. Zakas)
  • 71f6f0d feat: report more cases with ?? in no-constant-binary-expression (#​16826) (Daiki Nishikawa)

Bug Fixes

Documentation

Chores

framer/motion

v10.0.1

Compare Source

Changed
  • Reducing keyframe pregeneration duration by 75%.
vercel/turbo

v1.8.3: Turborepo v1.8.3

Compare Source

What's Changed

Changelog

New Contributors

Full Changelog: vercel/turbo@v1.8.2...v1.8.3

jquense/yup

v1.0.2

Compare Source

Bug Fixes

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.

@ijsblokjeee ijsblokjeee bot added Dependencies 🚀 PRs and Issues related to dependencies Chore 🧹 labels Mar 5, 2023
@kodiakhq kodiakhq bot merged commit 87c1c83 into main Mar 5, 2023
@kodiakhq kodiakhq bot deleted the renovate/all-minor-patch branch March 5, 2023 01:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Chore 🧹 Dependencies 🚀 PRs and Issues related to dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants