Bump babel-plugin-relay from 13.2.0 to 18.1.0 in /ui

[dependabot]

Bumps babel-plugin-relay from 13.2.0 to 18.1.0.

Release notes

Sourced from babel-plugin-relay's releases.

Version 18.1.0 Release Notes

Following up from our v18.0.0 release last month, v18.1.0 provides a number of fixes and improvements, adds some new experimental APIs, and ships some long-running experimental features as stable.

Relay Resolvers are now stable

For the past several years we've been iterating on Relay Resolvers which provided a structured and typesafe way to model client state and derived data in your GraphQL graph. As of this release, Relay Resolvers are enabled by default and no-longer experimental. As part of this stabilization we shipped fixes for Relay Resolvers when used with TypeScript and fixed a few edge cases related to how errors encountered by resolvers are handled.

• [d10786]: Update docs now that resolvers are stable by Jordan Eldredge
• [4e5377]: Remove Relay Resolver compiler feature flag by Jordan Eldredge
• [7b8f1f]: Remove ENABLE_RELAY_RESOLVERS runtime feature flag by Jordan Eldredge
• [1467b6]: Stabilize LiveResolverStore as the new implementation of RelayModernStore (#4806) by Jordan Eldredge
• [dec5ee]: Avoid running resolver code if root fragment throws with @​required(action: THROW) (#4799) by Jordan Eldredge
• [478274]: Ensure we import the type of a resolver for RelayResolverValue fields by Jordan Eldredge
• [852fbc]: Improve edge resolver error messages by Gordy French
• [575f20]: Add satisfies type assertion for typescript (#4797) by Drew Atkinson
• [2314f4]: Document relay field logger (#4809) by Jordan Eldredge

Improvements to error @​catch

We released @catch in v18.0.0 and are very excited about the capabilities it enables. Check out Itamar Kestenbaum's GraphQL conf talk about it here: Build Confidently: How @​Catch and Error Handling Pave Way in Field Nullability.

Since that release we've made a few improvements:

• Fields within a @catch directive that are marked as @semanticNonNull in the schema now generate non-nullable TypeScript/Flow types. See semantic nullability.
• Errors exposed to product code by @catch no-longer include the error message. This is because GraphQL error messages are generally not safe to show to users. These error messages can still be accessed by the field logger provided to your Relay Environment. In the future we plan to let users opt into allowing safe error messages through to product code.

• [26b78d]: Take advantage of @​semanticNonNull within @​catch (#4794) by Jordan Eldredge
• [6a038d]: Replace actual server-side error with generic "server error" message by Itamar Kestenbaum
• [6c8827]: Don't report missing fields within an unmatched inline fragment by Jordan Eldredge
• [2314f4]: Document relay field logger (#4809) by Jordan Eldredge

Compiler Error Reporting

We've improved how errors are reported by the Relay compiler to ensure we report as many errors as possible, and each error includes sufficient context.

• [9edbb0]: Report validation errors for all segements of a proejct by Jordan Eldredge
• [adaf8a]: Report location of operation that does not define variable by Jordan Eldredge

New "Copy Operation" VSCode command

Our VSCode extension now includes a command to quickly copy the full text of a query directly from within your editor.

• [8d2380]: Add copy operation command (#4778) by Tobias Tengler

Experimental APIs for reading fragment data outside of React

In some cases it can be useful to read a fragment outside of a React hook. However, doing this requires handling a number of concerns.

... (truncated)

Commits

• 3c0fa54 v18.1.0
• faa0244 Update hermes-parser and related packages in fbsource to 0.24.0
• 563e04f v18.0.0
• c072714 update babel and fix tests accordingly
• e1668bb Update hermes-parser and related packages in fbsource to 0.23.1
• 8cbb59e Update hermes-parser and related packages in fbsource to 0.23.0
• 5402ff5 v17.0.0
• 9a8d29c Update hermes-parser and related packages in fbsource to 0.22.0
• d5422ea Update hermes-parser and related packages to 0.21.1
• cdfd49f Fix sync of Relay runtime code to WWW
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

The following labels could not be found: kind/chore, pr/dependencies.