Bump rescript from 9.1.4 to 10.1.4

[dependabot]

Bumps rescript from 9.1.4 to 10.1.4.

Release notes

Sourced from rescript's releases.

10.1.4

🐛 Bug Fix

• Fix implementation of directives rescript-lang/rescript-compiler#6052
• Fix issue if the lib dir is included in the sources of bsconfig.json rescript-lang/rescript-compiler#6055
• Fix issue with string escape in pattern match rescript-lang/rescript-compiler#6062
• Fix issue with literal comparison of string constants rescript-lang/rescript-compiler#6065

🚀 New Feature

• Add support for toplevel await rescript-lang/rescript-compiler#6054

💅 Polish

• Better error message for extension point rescript-lang/rescript-compiler#6057
• Improve format check help rescript-lang/rescript-compiler#6056
• Deprecate unsafe j`$(a)$(b)` interpolation: use string templates `${a}${b}` instead rescript-lang/rescript-compiler#6067

10.1.3

🚀 New Feature

• Add experimental suppport for directives. An annotation such as @@directive("use client;") emits use client; verbatim before imports rescript-lang/rescript-compiler#5999
• genType: add Core standard library support for the following builtin types: Null.t, Nullable.t, Undefined.t, Dict.t<_>, Promise.t<_>, Date.t, BigInt.t, RegExp.t, Map.t<_, _>, WeakMap.t<_, _>, Set<_>, WeakSet<_> rescript-lang/rescript-compiler#6024

💥 Breaking Change

• genType: streamline the treatment of optionals as undefined rescript-lang/rescript-compiler#6024
  • Represent option<t> as undefined | t instead of null | undefined | t. This is more permissive when importing functions taking optional values (allows to use option types), but stricter when e.g. exporting ReScript functions taking arguments of option type. Fallback: use Js.undefined<_> instead.
  • Represent {x:option<string>} as {x:(undefined | string)} instead of {x?: string}. This is more in line with TS's behaviour. Fallback: use {x?:string}.

💅 Polish

• Add the gap property to jsxDOMStyle rescript-lang/rescript-compiler#5956

🐛 Bug Fix

• Fix issue where error messages related to non-existent props were displayed without location information rescript-lang/syntax#730
• Fix issue where uncurried functions were incorrectly converting the type of a prop given as a default value to curried rescript-lang/syntax#731
• Fix issue with nested async functions, where the inner function would be emitted without async rescript-lang/rescript-compiler#5984
• Fix issue with printing async functions with locally abstract types rescript-lang/syntax#732
• Fix issue with async context and locally abstract types rescript-lang/rescript-compiler#5985
• Fix support for recursive components in JSX V4 rescript-lang/syntax#733
• GenType: fix issue with V3 compatibility mode (see rescript-lang/rescript-compiler#5990) rescript-lang/rescript-compiler#5992
• Fix issue with overlapping labelled argument with default value rescript-lang/syntax#734
• Fix issue with using alias and default value together rescript-lang/syntax#734
• Fix issue in Js.Promise2 where then and catch were returning undefined rescript-lang/rescript-compiler#5996
• Fix issue in the compiler back-end where async functions passed to an @uncurry external would be inlined and transformed in a way that loses async rescript-lang/rescript-compiler#6011
• Fix location issue for the treatment of async functions where hovering on the body with a type error would show 'a => promise<'a> everywhere rescript-lang/rescript-compiler#6014
• Fix formatting of switch expressions that contain braced cases inside rescript-lang/syntax#735
• Fix formatting of props spread for multiline JSX expression rescript-lang/syntax#736
• Support @gentype.import as an alias to @genType.import in the compiler rescript-lang/rescript-compiler#6021
• In GenType, check annotations also in module types to decide whether to produce the .gen.tsx file rescript-lang/rescript-compiler#5903
• Fix issue with JSX V4 and newtype rescript-lang/syntax#737

... (truncated)

Changelog

Sourced from rescript's changelog.

10.1.4

🐛 Bug Fix

• Fix implementation of directives rescript-lang/rescript-compiler#6052
• Fix issue if the lib dir is included in the sources of bsconfig.json rescript-lang/rescript-compiler#6055
• Fix issue with string escape in pattern match rescript-lang/rescript-compiler#6062
• Fix issue with literal comparison of string constants rescript-lang/rescript-compiler#6065

🚀 New Feature

• Add support for toplevel await rescript-lang/rescript-compiler#6054

💅 Polish

• Better error message for extension point rescript-lang/rescript-compiler#6057
• Improve format check help rescript-lang/rescript-compiler#6056
• Deprecate unsafe j`$(a)$(b)` interpolation: use string templates `${a}${b}` instead rescript-lang/rescript-compiler#6067

10.1.3

🚀 New Feature

• Add experimental suppport for directives. An annotation such as @@directive("use client;") emits use client; verbatim before imports rescript-lang/rescript-compiler#5999
• genType: add Core standard library support for the following builtin types: Null.t, Nullable.t, Undefined.t, Dict.t<_>, Promise.t<_>, Date.t, BigInt.t, RegExp.t, Map.t<_, _>, WeakMap.t<_, _>, Set<_>, WeakSet<_> rescript-lang/rescript-compiler#6024

💥 Breaking Change

• genType: streamline the treatment of optionals as undefined rescript-lang/rescript-compiler#6024
  • Represent option<t> as undefined | t instead of null | undefined | t. This is more permissive when importing functions taking optional values (allows to use option types), but stricter when e.g. exporting ReScript functions taking arguments of option type. Fallback: use Js.undefined<_> instead.
  • Represent {x:option<string>} as {x:(undefined | string)} instead of {x?: string}. This is more in line with TS's behaviour. Fallback: use {x?:string}.

💅 Polish

• Add the gap property to jsxDOMStyle rescript-lang/rescript-compiler#5956

🐛 Bug Fix

• Fix issue where error messages related to non-existent props were displayed without location information rescript-lang/syntax#730
• Fix issue where uncurried functions were incorrectly converting the type of a prop given as a default value to curried rescript-lang/syntax#731
• Fix issue with nested async functions, where the inner function would be emitted without async rescript-lang/rescript-compiler#5984
• Fix issue with printing async functions with locally abstract types rescript-lang/syntax#732
• Fix issue with async context and locally abstract types rescript-lang/rescript-compiler#5985
• Fix support for recursive components in JSX V4 rescript-lang/syntax#733
• GenType: fix issue with V3 compatibility mode (see rescript-lang/rescript-compiler#5990) rescript-lang/rescript-compiler#5992
• Fix issue with overlapping labelled argument with default value rescript-lang/syntax#734
• Fix issue with using alias and default value together rescript-lang/syntax#734
• Fix issue in Js.Promise2 where then and catch were returning undefined rescript-lang/rescript-compiler#5996
• Fix issue in the compiler back-end where async functions passed to an @uncurry external would be inlined and transformed in a way that loses async rescript-lang/rescript-compiler#6011
• Fix location issue for the treatment of async functions where hovering on the body with a type error would show 'a => promise<'a> everywhere rescript-lang/rescript-compiler#6014
• Fix formatting of switch expressions that contain braced cases inside rescript-lang/syntax#735
• Fix formatting of props spread for multiline JSX expression rescript-lang/syntax#736

... (truncated)

Commits

• 3ac19a5 Deprecate unsafe j`$(a)$(b)` interpolation
• 6178dce Fix issue with comparison of string constants
• aea9227 polish(format): improv format check help (v10.1) (#6056)
• 96fdd85 Fix issue with pattern match escape. (#6062)
• a8e7876 snapshot
• f4a47e0 add error if the lib dir is included in the sources (v10.1) (#6055)
• d2427e8 Better error message extension (v10.1) (#6057)
• 4e78a3d Add support for toplevel await.
• b77be05 Fix implementation of directives.
• 37e105f Fix implementation of directives.
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by cknittel, a new releaser for rescript since your current version.

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 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)