Skip to content

chore(deps): update app dependencies #1295

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

Merged
merged 1 commit into from
Jun 10, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 6, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sanity/client (source) 6.19.1 -> 6.19.2 age adoption passing confidence
@sanity/icons (source) 3.0.0 -> 3.2.0 age adoption passing confidence
@sanity/pkg-utils 6.9.0 -> 6.9.3 age adoption passing confidence
@sanity/presentation (source) 1.15.13 -> 1.15.14 age adoption passing confidence
@sanity/ui (source) 2.2.0 -> 2.3.1 age adoption passing confidence
@sanity/visual-editing (source) 2.1.3 -> 2.1.4 age adoption passing confidence
esbuild ^0.21.4 -> ^0.21.5 age adoption passing confidence

Release Notes

sanity-io/client (@​sanity/client)

v6.19.2

Compare Source

Bug Fixes
sanity-io/icons (@​sanity/icons)

v3.2.0

Compare Source

Features

v3.1.0

Compare Source

Features
sanity-io/pkg-utils (@​sanity/pkg-utils)

v6.9.3

Compare Source

Bug Fixes

v6.9.2

Compare Source

Bug Fixes

v6.9.1

Compare Source

Bug Fixes
sanity-io/visual-editing (@​sanity/presentation)

v1.15.14

Dependencies
sanity-io/ui (@​sanity/ui)

v2.3.1

Compare Source

Bug Fixes

v2.3.0

Compare Source

Features
sanity-io/visual-editing (@​sanity/visual-editing)

v2.1.4

Bug Fixes
Dependencies
evanw/esbuild (esbuild)

v0.21.5

Compare Source

  • Fix Symbol.metadata on classes without a class decorator (#​3781)

    This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

  • Allow unknown import attributes to be used with the copy loader (#​3792)

    Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

    // This is an error with "--bundle" without also using "--external:./bagel.js"
    import tasty from "./bagel.js" with { type: "bagel" }

    Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

    However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

    // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
    import tasty from "./tasty.bagel" with { type: "bagel" }
  • Support import attributes with glob-style imports (#​3797)

    This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

    async function loadLocale(locale: string): Locale {
      const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
      return unpackLocale(locale, data)
    }

    Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

    ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data
    
        example.ts:2:28:
          2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
            ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~
    

    In addition, this change means plugins can now access the contents of with for glob-style imports.

  • Support ${configDir} in tsconfig.json files (#​3782)

    This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

    {
      "compilerOptions": {
        "paths": {
          "js/*": ["${configDir}/dist/js/*"]
        }
      }
    }

    You can read more in TypeScript's blog post about their upcoming 5.5 release. Note that this feature does not make use of template literals (you need to use "${configDir}/dist/js/*" not `${configDir}/dist/js/*`). The syntax for tsconfig.json is still just JSON with comments, and JSON syntax does not allow template literals. This feature only recognizes ${configDir} in strings for certain path-like properties, and only at the beginning of the string.

  • Fix internal error with --supported:object-accessors=false (#​3794)

    This release fixes a regression in 0.21.0 where some code that was added to esbuild's internal runtime library of helper functions for JavaScript decorators fails to parse when you configure esbuild with --supported:object-accessors=false. The reason is that esbuild introduced code that does { get [name]() {} } which uses both the object-extensions feature for the [name] and the object-accessors feature for the get, but esbuild was incorrectly only checking for object-extensions and not for object-accessors. Additional tests have been added to avoid this type of issue in the future. A workaround for this issue in earlier releases is to also add --supported:object-extensions=false.


Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (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 using a curated preset maintained by Sanity. View repository job log here

@renovate renovate bot requested a review from a team as a code owner June 6, 2024 11:11
Copy link

vercel bot commented Jun 6, 2024

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

Name Status Preview Comments Updated (UTC)
preview-kit-next-app-router ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 10, 2024 9:25am
preview-kit-next-pages-router ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 10, 2024 9:25am
preview-kit-remix ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 10, 2024 9:25am
preview-kit-test-studio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 10, 2024 9:25am
6 Ignored Deployments
Name Status Preview Comments Updated (UTC)
preview-kit-next-app-router-groq-store ⬜️ Ignored (Inspect) Visit Preview Jun 10, 2024 9:25am
preview-kit-next-app-router-live-store ⬜️ Ignored (Inspect) Visit Preview Jun 10, 2024 9:25am
preview-kit-next-pages-router-groq-store ⬜️ Ignored (Inspect) Visit Preview Jun 10, 2024 9:25am
preview-kit-next-pages-router-live-store ⬜️ Ignored (Inspect) Visit Preview Jun 10, 2024 9:25am
preview-kit-remix-groq-store ⬜️ Ignored (Inspect) Visit Preview Jun 10, 2024 9:25am
preview-kit-remix-live-store ⬜️ Ignored (Inspect) Visit Preview Jun 10, 2024 9:25am

Copy link

socket-security bot commented Jun 6, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@sanity/[email protected] None 0 0 B
npm/@sanity/[email protected] None 0 0 B
npm/@sanity/[email protected] None 0 0 B

View full report↗︎

@renovate renovate bot force-pushed the renovate/app-dependencies branch from ab61802 to e1b5659 Compare June 6, 2024 15:36
@renovate renovate bot force-pushed the renovate/app-dependencies branch from e1b5659 to 18fe081 Compare June 7, 2024 12:39
@renovate renovate bot force-pushed the renovate/app-dependencies branch from 18fe081 to 28758d7 Compare June 7, 2024 21:21
@renovate renovate bot force-pushed the renovate/app-dependencies branch from 28758d7 to 415c5ba Compare June 9, 2024 22:30
@stipsan stipsan merged commit f45c494 into main Jun 10, 2024
21 checks passed
@stipsan stipsan deleted the renovate/app-dependencies branch June 10, 2024 10:37
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant