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 non-major #107

Merged
merged 1 commit into from
May 28, 2024
Merged

chore(deps): update non-major #107

merged 1 commit into from
May 28, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 28, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@babel/core (source) ^7.24.4 -> ^7.24.6 age adoption passing confidence devDependencies patch
@commitlint/cli (source) ^19.2.1 -> ^19.3.0 age adoption passing confidence devDependencies minor
@commitlint/config-conventional (source) ^19.1.0 -> ^19.2.2 age adoption passing confidence devDependencies minor
@sanity/pkg-utils ^6.4.1 -> ^6.8.18 age adoption passing confidence devDependencies minor
@typescript-eslint/eslint-plugin (source) ^7.6.0 -> ^7.11.0 age adoption passing confidence devDependencies minor
@typescript-eslint/parser (source) ^7.6.0 -> ^7.11.0 age adoption passing confidence devDependencies minor
esbuild ^0.20.2 -> ^0.21.4 age adoption passing confidence devDependencies minor
peter-evans/create-pull-request 70a41ab -> 6d6857d action digest
prettier-plugin-packagejson ^2.4.14 -> ^2.5.0 age adoption passing confidence devDependencies minor

Release Notes

babel/babel (@​babel/core)

v7.24.6

Compare Source

🐛 Bug Fix
  • babel-helper-create-class-features-plugin, babel-plugin-transform-class-properties
  • babel-core, babel-generator, babel-plugin-transform-modules-commonjs
  • babel-helper-create-class-features-plugin, babel-plugin-proposal-decorators
  • babel-helpers, babel-plugin-proposal-decorators, babel-runtime-corejs3
  • babel-parser, babel-plugin-transform-typescript
🏠 Internal
  • babel-core, babel-helpers, babel-plugin-transform-runtime, babel-preset-env, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • babel-helpers
  • babel-cli, babel-helpers, babel-plugin-external-helpers, babel-plugin-proposal-decorators, babel-plugin-transform-class-properties, babel-plugin-transform-modules-commonjs, babel-plugin-transform-modules-systemjs, babel-plugin-transform-runtime, babel-preset-env, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • babel-parser, babel-traverse
  • Other

v7.24.5

Compare Source

🐛 Bug Fix
💅 Polish
🏠 Internal
  • Other
  • babel-parser
  • babel-helper-create-class-features-plugin, babel-helper-member-expression-to-functions, babel-helper-module-transforms, babel-helper-split-export-declaration, babel-helper-wrap-function, babel-helpers, babel-plugin-bugfix-firefox-class-in-computed-class-key, babel-plugin-proposal-explicit-resource-management, babel-plugin-transform-block-scoping, babel-plugin-transform-destructuring, babel-plugin-transform-object-rest-spread, babel-plugin-transform-optional-chaining, babel-plugin-transform-parameters, babel-plugin-transform-private-property-in-object, babel-plugin-transform-react-jsx-self, babel-plugin-transform-typeof-symbol, babel-plugin-transform-typescript, babel-traverse
  • babel-plugin-proposal-partial-application, babel-types
  • babel-plugin-transform-class-properties, babel-preset-env
🏃‍♀️ Performance
  • babel-helpers, babel-preset-env, babel-runtime-corejs3
conventional-changelog/commitlint (@​commitlint/cli)

v19.3.0

Compare Source

Note: Version bump only for package @​commitlint/cli

19.2.2 (2024-04-14)

Note: Version bump only for package @​commitlint/cli

19.2.1 (2024-03-19)

Note: Version bump only for package @​commitlint/cli

v19.2.2

Compare Source

Note: Version bump only for package @​commitlint/cli

conventional-changelog/commitlint (@​commitlint/config-conventional)

v19.2.2

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

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

v6.8.18

Compare Source

Bug Fixes

v6.8.17

Compare Source

Bug Fixes

v6.8.16

Compare Source

Bug Fixes

v6.8.15

Compare Source

Bug Fixes
  • only enable minifyInternalExports by default when minify: true (#​878) (ee50f48)

v6.8.14

Compare Source

Bug Fixes

v6.8.13

Compare Source

Bug Fixes

v6.8.12

Compare Source

Bug Fixes

v6.8.11

Compare Source

Bug Fixes

v6.8.10

Compare Source

Bug Fixes
  • @sanity/prettier-config is used in the init command (#​834) (7903bf3)
  • update init template to current best practices (#​835) (9acc566)

v6.8.9

Compare Source

Bug Fixes

v6.8.8

Compare Source

Bug Fixes

v6.8.7

Compare Source

Bug Fixes

v6.8.6

Compare Source

Bug Fixes
  • skip export conditions without a source (20612e7)

v6.8.4

Compare Source

Bug Fixes

v6.8.3

Compare Source

Bug Fixes

v6.8.2

Compare Source

Bug Fixes

v6.8.1

Compare Source

Bug Fixes

v6.8.0

Compare Source

Features
  • use @sanity/prettier-config (c9b1cc8)

v6.7.2

Compare Source

Bug Fixes
  • add shorter tsconfig preset paths (d67abcc)
  • allow export conditions that resolve to .json (3c677bc)

v6.7.1

Compare Source

Bug Fixes
  • recommended: add dom and dom.iterable to lib (d7be3bf)
  • strictest: add noImplicitOverride (4ee2f52)

v6.7.0

Compare Source

Features

v6.6.7

Compare Source

Bug Fixes

v6.6.6

Compare Source

Bug Fixes

v6.6.5

Compare Source

Bug Fixes
  • always fail the build on errors, not just on --strict (#​746) (aa601dc)

v6.6.4

Compare Source

Bug Fixes

v6.6.3

Compare Source

Bug Fixes

v6.6.2

Compare Source

Bug Fixes

v6.6.1

Compare Source

Bug Fixes

v6.6.0

Compare Source

Features

v6.5.0

Compare Source

Features
  • add strictOptions to config to toggle --strict checks (#​724) (396ce6c)
Bug Fixes
  • deps: Update dependency prettier-plugin-packagejson to ^2.5.0 (#​722) (1c5f7d3)
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v7.11.0

Compare Source

🚀 Features
  • eslint-plugin: deprecate prefer-ts-expect-error in favor of ban-ts-comment
🩹 Fixes
  • eslint-plugin: [consistent-type-assertions] prevent syntax errors on arrow functions
❤️ Thank You
  • Abraham Guo
  • auvred
  • Dom Armstrong
  • Kirk Waiblinger

You can read about our versioning strategy and releases on our website.

v7.10.0

Compare Source

🚀 Features
  • eslint-plugin: [sort-type-constituents] support case sensitive sorting
🩹 Fixes
  • eslint-plugin: [prefer-regexp-exec] fix heuristic to check whether regex may contain global flag
❤️ Thank You
  • auvred
  • Emanuel Hoogeveen
  • jsfm01
  • Kirk Waiblinger

You can read about our versioning strategy and releases on our website.

v7.9.0

Compare Source

🩹 Fixes
  • eslint-plugin: [explicit-function-return-types] fix false positive on default parameters
❤️ Thank You
  • Kirk Waiblinger
  • Sheetal Nandi
  • Vinccool96

You can read about our versioning strategy and releases on our website.

v7.8.0

Compare Source

🩹 Fixes

  • eslint-plugin: [no-unsafe-argument] handle tagged templates

  • eslint-plugin: [prefer-optional-chain] suggests optional chaining during strict null equality check

  • eslint-plugin: [consistent-type-assertions] handle tagged templates

  • eslint-plugin: [no-unsafe-return] handle union types

  • eslint-plugin: [no-unused-vars] clear error report range

❤️ Thank You
  • auvred
  • Josh Goldberg ✨
  • jsfm01
  • Kim Sang Du
  • YeonJuan

You can read about our versioning strategy and releases on our website.

v7.7.1

Compare Source

🩹 Fixes

  • eslint-plugin: [no-unsafe-assignment] handle shorthand property assignment

  • eslint-plugin: [explicit-function-return-type] fix checking wrong ancestor's return type

  • eslint-plugin: [prefer-optional-chain] only look at left operand for requireNullish

  • eslint-plugin: [no-for-in-array] refine report location

  • eslint-plugin: [no-unnecessary-type-assertion] allow non-null assertion for void type

❤️ Thank You
  • Abraham Guo
  • Kirk Waiblinger
  • YeonJuan

You can read about our versioning strategy and releases on our website.

v7.7.0

Compare Source

🚀 Features
  • eslint-plugin: replace no-new-symbol with no-new-native-nonconstructor
❤️ Thank You
  • Dave
  • Josh Goldberg ✨

You can read about our versioning strategy and releases on our website.

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

v7.11.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.10.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.9.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.8.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.7.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.7.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

evanw/esbuild (esbuild)

v0.21.4

Compare Source

  • Update support for import assertions and import attributes in node (#​3778)

    Import assertions (the assert keyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with --target=node22 or above:

    ▲ [WARNING] The "assert" keyword is not supported in the configured target environment ("node22") [assert-to-with]

    example.mjs:1:40:
      1 │ import json from "esbuild/package.json" assert { type: "json" }
        │                                         ~~~~~~
        ╵                                         with

  Did you mean to use "with" instead of "assert"?

    Import attributes (the with keyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with --target=node18.N if N is 20 or greater.

  • Fix for await transform when a label is present

    This release fixes a bug where the for await transform, which wraps the loop in a try statement, previously failed to also move the loop's label into the try statement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:

    // Original code
async function test() {
  outer: for await (const x of [Promise.resolve([0, 1])]) {
    for (const y of x) if (y) break outer
    throw 'fail'
  }
}

// Old output (with --target=es6)
function test() {
  return __async(this, null, function* () {
    outer: try {
      for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
        const x = temp.value;
        for (const y of x) if (y) break outer;
        throw "fail";
      }
    } catch (temp) {
      error = [temp];
    } finally {
      try {
        more && (temp = iter.return) && (yield temp.call(iter));
      } finally {
        if (error)
          throw error[0];
      }
    }
  });
}

// New output (with --target=es6)
function test() {
  return __async(this, null, function* () {
    try {
      outer: for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
        const x = temp.value;
        for (const y of x) if (y) break outer;
        throw "fail";
      }
    } catch (temp) {
      error = [temp];
    } finally {
      try {
        more && (temp = iter.return) && (yield temp.call(iter));
      } finally {
        if (error)
          throw error[0];
      }
    }
  });
}

  • Do additional constant folding after cross-module enum inlining (#​3416, #​3425)

    This release adds a few more cases where esbuild does constant folding after cross-module enum inlining.

    // Original code: enum.ts
export enum Platform {
  WINDOWS = 'windows',
  MACOS = 'macos',
  LINUX = 'linux',
}

// Original code: main.ts
import { Platform } from './enum';
declare const PLATFORM: string;
export function logPlatform() {
  if (PLATFORM == Platform.WINDOWS) console.log('Windows');
  else if (PLATFORM == Platform.MACOS) console.log('macOS');
  else if (PLATFORM == Platform.LINUX) console.log('Linux');
  else console.log('Other');
}

// Old output (with --bundle '--define:PLATFORM="macos"' --minify --format=esm)
function n(){"windows"=="macos"?console.log("Windows"):"macos"=="macos"?console.log("macOS"):"linux"=="macos"?console.log("Linux"):console.log("Other")}export{n as logPlatform};

// New output (with --bundle '--define:PLATFORM="macos"' --minify --format=esm)
function n(){console.log("macOS")}export{n as logPlatform};

  • Pass import attributes to on-resolve plugins (#​3384, #​3639, #​3646)

    With this release, on-resolve plugins will now have access to the import attributes on the import via the with property of the arguments object. This mirrors the with property of the arguments object that's already passed to on-load plugins. In addition, you can now pass with to the resolve() API call which will then forward that value on to all relevant plugins. Here's an example of a plugin that can now be written:

    const examplePlugin = {
  name: 'Example plugin',
  setup(build) {
    build.onResolve({ filter: /.*/ }, args => {
      if (args.with.type === 'external')
        return { external: true }
    })
  }
}

require('esbuild').build({
  stdin: {
    contents: `
      import foo from "./foo" with { type: "external" }
      foo()
    `,
  },
  bundle: true,
  format: 'esm',
  write: false,
  plugins: [examplePlugin],
}).then(result => {
  console.log(result.outputFiles[0].text)
})

  • Formatting support for the @position-try rule (#​3773)

    Chrome shipped this new CSS at-rule in version 125 as part of the CSS anchor positioning API. With this release, esbuild now knows to expect a declaration list inside of the @position-try body block and will format it appropriately.

  • Always allow internal string import and export aliases (#​3343)

    Import and export names can be string literals in ES2022+. Previously esbuild forbid any usage of these aliases when the target was below ES2022. Starting with this release, esbuild will only forbid such usage when the alias would otherwise end up in output as a string literal. String literal aliases that are only used internally in the bundle and are "compiled away" are no longer errors. This makes it possible to use string literal aliases with esbuild's inject feature even when the target is earlier than ES2022.

v0.21.3

Compare Source

  • Implement the decorator metadata proposal (#​3760)

    This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:

    // Shim the "Symbol.metadata" symbol
Symbol.metadata ??= Symbol('Symbol.metadata')

const track = (_, context) => {
  (context.metadata.names ||= []).push(context.name)
}

class Foo {
  @​track foo = 1
  @​track bar = 2
}

// Prints ["foo", "bar"]
console.log(Foo[Symbol.metadata].names)

    ⚠️ WARNING ⚠️

    This proposal has been marked as "stage 3" which means "recommended for implementation". 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 decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

  • Fix bundled decorators in derived classes (#​3768)

    In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:

    class Foo extends Object {
  @​(x => x) foo() {
    return Foo
  }
}
console.log(new Foo().foo())

  • Fix tsconfig.json files inside symlinked directories (#​3767)

    This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.

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 { @​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: /* @​__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 {
  @​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-m

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (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

@socket-security Socket Security
Copy link

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

Package New capabilities Transitives Size Publisher

🚮 Removed packages: npm/esbuild@0.20.2

View full report↗︎

@stipsan stipsan enabled auto-merge May 28, 2024 10:45
@stipsan stipsan added this pull request to the merge queue May 28, 2024
Merged via the queue into main with commit 7f27a2f May 28, 2024
7 checks passed
@stipsan stipsan deleted the renovate/non-major branch May 28, 2024 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@stipsan stipsan stipsan approved these changes

Assignees
No one assigned
Labels
🤖 bot 📦 deps
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@stipsan