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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update driver adapters directory (minor) #4843

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update driver adapters directory (minor) #4843

wants to merge 1 commit into from
+8 −8

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 27, 2024 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@cloudflare/workers-types 4.20240405.0 -> 4.20240502.0 age adoption passing confidence
@effect/schema (source) 0.64.20 -> 0.67.0 age adoption passing confidence
esbuild 0.20.2 -> 0.21.2 age adoption passing confidence
tsx 4.7.2 -> 4.10.1 age adoption passing confidence
undici (source) 6.13.0 -> 6.16.1 age adoption passing confidence
wrangler (source) 3.50.0 -> 3.55.0 age adoption passing confidence
ws 8.16.0 -> 8.17.0 age adoption passing confidence

Release Notes

cloudflare/workerd (@​cloudflare/workers-types)

v4.20240502.0

Compare Source

v4.20240423.0

Compare Source

v4.20240419.0

Compare Source

Effect-TS/effect (@​effect/schema)

v0.67.0

Compare Source

Minor Changes

  • #​2634 d7e4997 Thanks @​gcanti! - ## Simplifying Type Extraction

    When we work with schemas, it's common to need to extract their types automatically.
    To make this easier, we've made some changes to the Schema interface.
    Now, you can easily access Type and Encoded directly from a schema without the need for Schema.Schema.Type and Schema.Schema.Encoded.

    import { Schema } from "@​effect/schema";

const PersonSchema = Schema.Struct({
  name: Schema.String,
  age: Schema.NumberFromString,
});

// same as type PersonType = Schema.Schema.Type<typeof PersonSchema>
type PersonType = typeof PersonSchema.Type;

// same as Schema.Schema.Encoded<typeof PersonSchema>
type PersonEncoded = typeof PersonSchema.Encoded;

v0.66.16

Compare Source

Patch Changes
  • Updated dependencies [1f6dc96]:
    • effect@3.1.3

v0.66.15

Compare Source

Patch Changes

v0.66.14

Compare Source

Patch Changes

v0.66.13

Compare Source

Patch Changes
  • Updated dependencies [e5e56d1]:
    • effect@3.1.1

v0.66.12

Compare Source

Patch Changes

v0.66.11

Compare Source

Patch Changes

v0.66.10

Compare Source

Patch Changes
  • Updated dependencies [18de56b]:
    • effect@3.0.7

v0.66.9

Compare Source

Patch Changes

  • #​2626 027418e Thanks @​fubhy! - Reintroduce custom NoInfer type

  • #​2631 8206529 Thanks @​gcanti! - add support for data-last subtype overloads in compose

    Before

    import { Schema as S } from "@&#8203;effect/schema";

S.Union(S.Null, S.String).pipe(S.compose(S.NumberFromString)); // ts error
S.NumberFromString.pipe(S.compose(S.Union(S.Null, S.Number))); // ts error

    Now

    import { Schema as S } from "@&#8203;effect/schema";

// $ExpectType Schema<number, string | null, never>
S.Union(S.Null, S.String).pipe(S.compose(S.NumberFromString)); // ok
// $ExpectType Schema<number | null, string, never>
S.NumberFromString.pipe(S.compose(S.Union(S.Null, S.Number))); // ok

  • Updated dependencies [ffe4f4e, 027418e, ac1898e, ffe4f4e]:

    • effect@3.0.6

v0.66.8

Compare Source

Patch Changes

v0.66.7

Compare Source

Patch Changes

v0.66.6

Compare Source

Patch Changes

  • #​2586 9dfc156 Thanks @​gcanti! - remove non-tree-shakable compiler dependencies from the Schema module:

    • remove dependency from Arbitrary compiler
    • remove dependency from Equivalence compiler
    • remove dependency from Pretty compiler

  • #​2583 80271bd Thanks @​suddenlyGiovanni! - - Fixed a typo in the JSDoc comment of the BooleanFromUnknown boolean constructors in Schema.ts

    • Fixed a typo in the JSDoc comment of the split string transformations combinator in Schema.ts

  • #​2585 e4ba97d Thanks @​gcanti! - JSONSchema: rearrange handling of surrogate annotations to occur after JSON schema annotations

v0.66.5

Compare Source

Patch Changes

  • #​2582 b3fe829 Thanks @​gcanti! - Add default title annotations to both sides of Struct transformations.

    This simple addition helps make error messages shorter and more understandable.

    Before

    import { Schema } from "@&#8203;effect/schema";

const schema = Schema.Struct({
  a: Schema.optional(Schema.String, { exact: true, default: () => "" }),
  b: Schema.String,
  c: Schema.String,
  d: Schema.String,
  e: Schema.String,
  f: Schema.String,
});

Schema.decodeUnknownSync(schema)({ a: 1 });
/*
throws
Error: ({ a?: string; b: string; c: string; d: string; e: string; f: string } <-> { a: string; b: string; c: string; d: string; e: string; f: string })
└─ Encoded side transformation failure
   └─ { a?: string; b: string; c: string; d: string; e: string; f: string }
      └─ ["a"]
         └─ Expected a string, actual 1
*/

    Now

    import { Schema } from "@&#8203;effect/schema";

const schema = Schema.Struct({
  a: Schema.optional(Schema.String, { exact: true, default: () => "" }),
  b: Schema.String,
  c: Schema.String,
  d: Schema.String,
  e: Schema.String,
  f: Schema.String,
});

Schema.decodeUnknownSync(schema)({ a: 1 });
/*
throws
Error: (Struct (Encoded side) <-> Struct (Type side))
└─ Encoded side transformation failure
   └─ Struct (Encoded side)
      └─ ["a"]
         └─ Expected a string, actual 1
*/

  • #​2581 a58b7de Thanks @​gcanti! - Fix formatting for Class and brands AST.

  • #​2579 d90e8c3 Thanks @​gcanti! - Schema: JSONSchema should support make(Class)

    Before

    import { JSONSchema, Schema } from "@&#8203;effect/schema";

class A extends Schema.Class<A>("A")({
  a: Schema.String,
}) {}

console.log(JSONSchema.make(A)); // throws MissingAnnotation: cannot build a JSON Schema for a declaration without a JSON Schema annotation

    Now

    console.log(JSONSchema.make(A));
/*
Output:
{
  '$schema': 'http://json-schema.org/draft-07/schema#',
  type: 'object',
  required: [ 'a' ],
  properties: { a: { type: 'string', description: 'a string', title: 'string' } },
  additionalProperties: false
}
*/

v0.66.4

Compare Source

Patch Changes

  • #​2577 773b8e0 Thanks @​gcanti! - partial / required: add support for renaming property keys in property signature transformations

    Before

    import { Schema } from "@&#8203;effect/schema";

const TestType = Schema.Struct({
  a: Schema.String,
  b: Schema.propertySignature(Schema.String).pipe(Schema.fromKey("c")),
});

const PartialTestType = Schema.partial(TestType);
// throws Error: Partial: cannot handle transformations

    Now

    import { Schema } from "@&#8203;effect/schema";

const TestType = Schema.Struct({
  a: Schema.String,
  b: Schema.propertySignature(Schema.String).pipe(Schema.fromKey("c")),
});

const PartialTestType = Schema.partial(TestType);

console.log(Schema.decodeUnknownSync(PartialTestType)({ a: "a", c: "c" })); // { a: 'a', b: 'c' }
console.log(Schema.decodeUnknownSync(PartialTestType)({ a: "a" })); // { a: 'a' }

const RequiredTestType = Schema.required(PartialTestType);

console.log(Schema.decodeUnknownSync(RequiredTestType)({ a: "a", c: "c" })); // { a: 'a', b: 'c' }
console.log(Schema.decodeUnknownSync(RequiredTestType)({ a: "a" })); // { a: 'a', b: undefined }

v0.66.3

Compare Source

Patch Changes
  • Updated dependencies [a7b4b84]:
    • effect@3.0.3

v0.66.2

Compare Source

Patch Changes

v0.66.1

Compare Source

Patch Changes

v0.66.0

Compare Source

Minor Changes
Patch Changes

v0.65.0

Compare Source

Minor Changes

For the updates mentioned below, we've released a codemod to simplify the migration process.

To run it, use the following command:

npx @&#8203;effect/codemod schema-0.65 src/**/*

The codemod is designed to automate many of the changes needed. However, it might not catch everything, so please let us know if you run into any issues (https://github.com/Effect-TS/codemod/issues). Remember to commit your code changes before running the codemod, just in case you need to undo anything.

evanw/esbuild (esbuild)

v0.21.2

Compare Source

  • Correct this in field and accessor decorators (#​3761)

    This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:

    const dec = () => function() { this.bar = true }
class Foo { @&#8203;dec static foo }
console.log(Foo.bar) // Should be "true"

  • Allow es2023 as a target environment (#​3762)

    TypeScript recently added es2023 as a compilation target, so esbuild now supports this too. There is no difference between a target of es2022 and es2023 as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features.

v0.21.1

Compare Source

  • Fix a regression with --keep-names (#​3756)

    The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:

    // Original code
x = { get y() {} }

// Output from version 0.21.0 (with --keep-names)
x = { get y: /* @&#8203;__PURE__ */ __name(function() {
}, "y") };

// Output from this version (with --keep-names)
x = { get y() {
} };

v0.21.0

Compare Source

This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.

  • Implement the JavaScript decorators proposal (#​104)

    With this release, esbuild now contains an implementation of the upcoming JavaScript decorators proposal. This is the same feature that shipped in TypeScript 5.0 and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: https://2ality.com/2022/10/javascript-decorators.html. Here's a quick example:

    const log = (fn, context) => function() {
  console.log(`before ${context.name}`)
  const it = fn.apply(this, arguments)
  console.log(`after ${context.name}`)
  return it
}

class Foo {
  @&#8203;log static foo() {
    console.log('in foo')
  }
}

// Logs "before foo", "in foo", "after foo"
Foo.foo()

    Note that this feature is different than the existing "TypeScript experimental decorators" feature that esbuild already implements. It uses similar syntax but behaves very differently, and the two are not compatible (although it's sometimes possible to write decorators that work with both). TypeScript experimental decorators will still be supported by esbuild going forward as they have been around for a long time, are very widely used, and let you do certain things that are not possible with JavaScript decorators (such as decorating function parameters). By default esbuild will parse and transform JavaScript decorators, but you can tell esbuild to parse and transform TypeScript experimental decorators instead by setting "experimentalDecorators": true in your tsconfig.json file.

    Probably at least half of the work for this feature went into creating a test suite that exercises many of the proposal's edge cases: https://github.com/evanw/decorator-tests. It has given me a reasonable level of confidence that esbuild's initial implementation is acceptable. However, I don't have access to a significant sample of real code that uses JavaScript decorators. If you're currently using JavaScript decorators in a real code base, please try out esbuild's implementation and let me know if anything seems off.

    ⚠️ WARNING ⚠️

    This proposal has been in the works for a very long time (work began around 10 years ago in 2014) and it is finally getting close to becoming part of the JavaScript language. However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorators may need to be updated as the feature continues to evolve. The decorators proposal is pretty close to its final form but it can and likely will undergo some small behavioral adjustments before it ends up becoming a part of the standard. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

  • Optimize the generated code for private methods

    Previously when lowering private methods for old browsers, esbuild would generate one WeakSet for each private method. This mirrors similar logic for generating one WeakSet for each private field. Using a separate WeakMap for private fields is necessary as their assignment can be observable:

    let it
class Bar {
  constructor() {
    it = this
  }
}
class Foo extends Bar {
  #x = 1
  #y = null.foo
  static check() {
    console.log(#x in it, #y in it)
  }
}
try { new Foo } catch {}
Foo.check()

    This prints true false because this partially-initialized instance has #x but not #y. In other words, it's not true that all class instances will always have all of their private fields. However, the assignment of private methods to a class instance is not observable. In other words, it's true that all class instances will always have all of their private methods. This means esbuild can lower private methods into code where all methods share a single WeakSet, which is smaller, faster, and uses less memory. Other JavaScript processing tools such as the TypeScript compiler already make this optimization. Here's what this change looks like:

    // Original code
class Foo {
  #x() { return this.#x() }
  #y() { return this.#y() }
  #z() { return this.#z() }
}

// Old output (--supported:class-private-method=false)
var _x, x_fn, _y, y_fn, _z, z_fn;
class Foo {
  constructor() {
    __privateAdd(this, _x);
    __privateAdd(this, _y);
    __privateAdd(this, _z);
  }
}
_x = new WeakSet();
x_fn = function() {
  return __privateMethod(this, _x, x_fn).call(this);
};
_y = new WeakSet();
y_fn = function() {
  return __privateMethod(this, _y, y_fn).call(this);
};
_z = new WeakSet();
z_fn = function() {
  return __privateMethod(this, _z, z_fn).call(this);
};

// New output (--supported:class-private-method=false)
var _Foo_instances, x_fn, y_fn, z_fn;
class Foo {
  constructor() {
    __privateAdd(this, _Foo_instances);
  }
}
_Foo_instances = new WeakSet();
x_fn = function() {
  return __privateMethod(this, _Foo_instances, x_fn).call(this);
};
y_fn = function() {
  return __privateMethod(this, _Foo_instances, y_fn).call(this);
};
z_fn = function() {
  return __privateMethod(this, _Foo_instances, z_fn).call(this);
};

  • Fix an obscure bug with lowering class members with computed property keys

    When class members that use newer syntax features are transformed for older target environments, they sometimes need to be relocated. However, care must be taken to not reorder any side effects caused by computed property keys. For example, the following code must evaluate a() then b() then c():

    class Foo {
  [a()]() {}
  [b()];
  static { c() }
}

    Previously esbuild did this by shifting the computed property key forward to the next spot in the evaluation order. Classes evaluate all computed keys first and then all static class elements, so if the last computed key needs to be shifted, esbuild previously inserted a static block at start of the class body, ensuring it came before all other static class elements:

    var _a;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  static {
    _a = b();
  }
  [a()]() {
  }
  static {
    c();
  }
}

    However, this could cause esbuild to accidentally generate a syntax error if the computed property key contains code that isn't allowed in a static block, such as an await expression. With this release, esbuild fixes this problem by shifting the computed property key backward to the previous spot in the evaluation order instead, which may push it into the extends clause or even before the class itself:

    // Original code
class Foo {
  [a()]() {}
  [await b()];
  static { c() }
}

// Old output (with --supported:class-field=false)
var _a;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  static {
    _a = await b();
  }
  [a()]() {
  }
  static {
    c();
  }
}

// New output (with --supported:class-field=false)
var _a, _b;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  [(_b = a(), _a = await b(), _b)]() {
  }
  static {
    c();
  }
}

  • Fix some --keep-names edge cases

    The NamedEvaluation syntax-directed operation in the JavaScript specification gives certain anonymous expressions a name property depending on where they are in the syntax tree. For example, the following initializers convey a name value:

    var foo = function() {}
var bar = class {}
console.log(foo.name, bar.name)

    When you enable esbuild's --keep-names setting, esbuild generates additional code to represent this NamedEvaluation operation so that the value of the name property persists even when the identifiers are renamed (e.g. due to minification).

    However, I recently learned that esbuild's implementation of NamedEvaluation is missing a few cases. Specifically esbuild was missing property definitions, class initializers, logical-assignment operators. These cases should now all be handled:

    var obj = { foo: function() {} }
class Foo0 { foo = function() {} }
class Foo1 { static foo = function() {} }
class Foo2 { accessor foo = function() {} }
class Foo3 { static accessor foo = function() {} }
foo ||= function() {}
foo &&= function() {}
foo ??= function() {}
privatenumber/tsx (tsx)

v4.10.1

Compare Source

v4.10.0

Compare Source

Features
  • esm api: register to return a namespaced import() method (53bb4aa)

This release is also available on:

v4.9.5

Compare Source

v4.9.4

Compare Source

Bug Fixes
  • tsImport: import module from commonjs (48f0a75)

This release is also available on:

v4.9.3

Compare Source

Bug Fixes

This release is also available on:

v4.9.2

Compare Source

Bug Fixes

This release is also available on:

v4.9.1

Compare Source

v4.9.0

Compare Source

v4.8.2

Compare Source

Bug Fixes
  • types: cjs/api to use .d.cts (4b1f03c)

This release is also available on:

v4.8.1

Compare Source

v4.8.0

Compare Source

v4.7.3

Compare Source

Bug Fixes
  • support TS resolution in JS files when allowJs is set (#​535) (081853e)

This release is also available on:

nodejs/undici (undici)

v6.16.1

Compare Source

What's Changed

Full Changelog: nodejs/undici@v6.16.0...v6.16.1

v6.16.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v6.15.0...v6.16.0

v6.15.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v6.14.1...v6.15.0

v6.14.1

Compare Source

What's Changed

Full Changelog: nodejs/undici@v6.14.0...v6.14.1

v6.14.0

Compare Source

What's Changed

Configuration

📅 Schedule: Branch creation - "every weekend" (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.

@renovate renovate bot requested a review from a team as a code owner April 27, 2024 00:34
@renovate renovate bot requested review from Weakky and removed request for a team April 27, 2024 00:34
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Apr 27, 2024 •
edited

WASM Query Engine file Size

Engine This PR Base branch Diff
Postgres 2.153MiB 2.153MiB 0.000B
Postgres (gzip) 846.060KiB 846.061KiB -1.000B
Mysql 2.119MiB 2.119MiB 0.000B
Mysql (gzip) 831.748KiB 831.749KiB -1.000B
Sqlite 2.015MiB 2.015MiB 0.000B
Sqlite (gzip) 793.080KiB 793.081KiB -1.000B

@codspeed-hq CodSpeed HQ
Copy link

codspeed-hq bot commented Apr 27, 2024 •
edited

CodSpeed Performance Report

Merging #4843 will not alter performance

Comparing renovate/driver-adapters-directory (f99c786) with main (0af42cb)

Summary

✅ 11 untouched benchmarks

@renovate renovate bot force-pushed the renovate/driver-adapters-directory branch 3 times, most recently from e4212fb to c2ec744 Compare May 4, 2024 10:17
@renovate renovate bot force-pushed the renovate/driver-adapters-directory branch 3 times, most recently from abeac44 to 643a2d0 Compare May 11, 2024 16:40
@renovate renovate bot force-pushed the renovate/driver-adapters-directory branch 4 times, most recently from 12b29a2 to 37dd300 Compare May 19, 2024 11:49
@renovate renovate bot force-pushed the renovate/driver-adapters-directory branch from 37dd300 to f99c786 Compare May 19, 2024 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Weakky Weakky Awaiting requested review from Weakky Weakky is a code owner automatically assigned from prisma/orm-rust

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants