Skip to content

chore(deps): update all non-major dependencies #89

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
Merged
merged 1 commit into from
Feb 1, 2023
Merged

chore(deps): update all non-major dependencies #89

merged 1 commit into from
Feb 1, 2023

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 1, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) ^18.11.13 -> ^18.11.18 age adoption passing confidence
@typescript-eslint/eslint-plugin ^5.46.0 -> ^5.50.0 age adoption passing confidence
@typescript-eslint/parser ^5.46.0 -> ^5.50.0 age adoption passing confidence
@vitest/coverage-istanbul ^0.27.0 -> ^0.28.3 age adoption passing confidence
esbuild ^0.17.0 -> ^0.17.5 age adoption passing confidence
eslint (source) ^8.29.0 -> ^8.33.0 age adoption passing confidence
eslint-config-prettier ^8.5.0 -> ^8.6.0 age adoption passing confidence
eslint-plugin-import ^2.26.0 -> ^2.27.5 age adoption passing confidence
prettier (source) ^2.8.1 -> ^2.8.3 age adoption passing confidence
release-it ^15.5.1 -> ^15.6.0 age adoption passing confidence
typescript (source) ^4.9.4 -> ^4.9.5 age adoption passing confidence
vitest ^0.27.0 -> ^0.28.3 age adoption passing confidence

Release Notes

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

v5.50.0

Compare Source

Bug Fixes
  • eslint-plugin: [ban-ts-comment] counts graphemes instead of String.prototype.length (#​5704) (09d57ce)
  • eslint-plugin: [prefer-optional-chain] fix ThisExpression and PrivateIdentifier errors (#​6028) (85e783c)
  • eslint-plugin: [prefer-optional-chain] fixer produces wrong logic (#​5919) (b0f6c8e), closes #​1438
Features
  • eslint-plugin: add key-spacing rule extension for interface & type declarations (#​6211) (67706e7)

v5.49.0

Compare Source

Features
  • eslint-plugin: [naming-convention] add support for #private modifier on class members (#​6259) (c8a6d80)

5.48.2 (2023-01-16)

Note: Version bump only for package @​typescript-eslint/eslint-plugin

5.48.1 (2023-01-09)

Note: Version bump only for package @​typescript-eslint/eslint-plugin

v5.48.2

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

v5.48.1

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

v5.48.0

Compare Source

Features
  • eslint-plugin: specify which method is unbound and added test case (#​6281) (cf3ffdd)

5.47.1 (2022-12-26)

Bug Fixes
  • ast-spec: correct some incorrect ast types (#​6257) (0f3f645)
  • eslint-plugin: [member-ordering] correctly invert optionalityOrder (#​6256) (ccd45d4)

v5.47.1

Compare Source

Bug Fixes
  • ast-spec: correct some incorrect ast types (#​6257) (0f3f645)
  • eslint-plugin: [member-ordering] correctly invert optionalityOrder (#​6256) (ccd45d4)

v5.47.0

Compare Source

Features
  • eslint-plugin: [no-floating-promises] add suggestion fixer to add an 'await' (#​5943) (9e35ef9)

5.46.1 (2022-12-12)

Note: Version bump only for package @​typescript-eslint/eslint-plugin

v5.46.1

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

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

v5.50.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.49.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

5.48.2 (2023-01-16)

Note: Version bump only for package @​typescript-eslint/parser

5.48.1 (2023-01-09)

Note: Version bump only for package @​typescript-eslint/parser

v5.48.2

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.48.1

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.48.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

5.47.1 (2022-12-26)

Note: Version bump only for package @​typescript-eslint/parser

v5.47.1

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.47.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

5.46.1 (2022-12-12)

Note: Version bump only for package @​typescript-eslint/parser

v5.46.1

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

vitest-dev/vitest

v0.28.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v0.28.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.28.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.28.0

Compare Source

   🚨 Breaking Changes
   🐞 Bug Fixes
    View changes on GitHub

v0.27.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.27.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v0.27.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
evanw/esbuild

v0.17.5

Compare Source

  • Parse const type parameters from TypeScript 5.0

    The TypeScript 5.0 beta announcement adds const type parameters to the language. You can now add the const modifier on a type parameter of a function, method, or class like this:

    type HasNames = { names: readonly string[] };
const getNamesExactly = <const T extends HasNames>(arg: T): T["names"] => arg.names;
const names = getNamesExactly({ names: ["Alice", "Bob", "Eve"] });

    The type of names in the above example is readonly ["Alice", "Bob", "Eve"]. Marking the type parameter as const behaves as if you had written as const at every use instead. The above code is equivalent to the following TypeScript, which was the only option before TypeScript 5.0:

    type HasNames = { names: readonly string[] };
const getNamesExactly = <T extends HasNames>(arg: T): T["names"] => arg.names;
const names = getNamesExactly({ names: ["Alice", "Bob", "Eve"] } as const);

    You can read the announcement for more information.

  • Make parsing generic async arrow functions more strict in .tsx files

    Previously esbuild's TypeScript parser incorrectly accepted the following code as valid:

    let fn = async <T> () => {};

    The official TypeScript parser rejects this code because it thinks it's the identifier async followed by a JSX element starting with <T>. So with this release, esbuild will now reject this syntax in .tsx files too. You'll now have to add a comma after the type parameter to get generic arrow functions like this to parse in .tsx files:

    let fn = async <T,> () => {};

  • Allow the in and out type parameter modifiers on class expressions

    TypeScript 4.7 added the in and out modifiers on the type parameters of classes, interfaces, and type aliases. However, while TypeScript supported them on both class expressions and class statements, previously esbuild only supported them on class statements due to an oversight. This release now allows these modifiers on class expressions too:

    declare let Foo: any;
Foo = class <in T> { };
Foo = class <out T> { };

  • Update enum constant folding for TypeScript 5.0

    TypeScript 5.0 contains an updated definition of what it considers a constant expression:

    An expression is considered a constant expression if it is

    • a number or string literal,
    • a unary +, -, or ~ applied to a numeric constant expression,
    • a binary +, -, *, /, %, **, <<, >>, >>>, |, &, ^ applied to two numeric constant expressions,
    • a binary + applied to two constant expressions whereof at least one is a string,
    • a template expression where each substitution expression is a constant expression,
    • a parenthesized constant expression,
    • a dotted name (e.g. x.y.z) that references a const variable with a constant expression initializer and no type annotation,
    • a dotted name that references an enum member with an enum literal type, or
    • a dotted name indexed by a string literal (e.g. x.y["z"]) that references an enum member with an enum literal type.

    This impacts esbuild's implementation of TypeScript's const enum feature. With this release, esbuild will now attempt to follow these new rules. For example, you can now initialize an enum member with a template literal expression that contains a numeric constant:

    // Original input
const enum Example {
  COUNT = 100,
  ERROR = `Expected ${COUNT} items`,
}
console.log(
  Example.COUNT,
  Example.ERROR,
)

// Old output (with --tree-shaking=true)
var Example = /* @&#8203;__PURE__ */ ((Example2) => {
  Example2[Example2["COUNT"] = 100] = "COUNT";
  Example2[Example2["ERROR"] = `Expected ${100 /* COUNT */} items`] = "ERROR";
  return Example2;
})(Example || {});
console.log(
  100 /* COUNT */,
  Example.ERROR
);

// New output (with --tree-shaking=true)
console.log(
  100 /* COUNT */,
  "Expected 100 items" /* ERROR */
);

    These rules are not followed exactly due to esbuild's limitations. The rule about dotted references to const variables is not followed both because esbuild's enum processing is done in an isolated module setting and because doing so would potentially require esbuild to use a type system, which it doesn't have. For example:

    // The TypeScript compiler inlines this but esbuild doesn't:
declare const x = 'foo'
const enum Foo { X = x }
console.log(Foo.X)

    Also, the rule that requires converting numbers to a string currently only followed for 32-bit signed integers and non-finite numbers. This is done to avoid accidentally introducing a bug if esbuild's number-to-string operation doesn't exactly match the behavior of a real JavaScript VM. Currently esbuild's number-to-string constant folding is conservative for safety.

  • Forbid definite assignment assertion operators on class methods

    In TypeScript, class methods can use the ? optional property operator but not the ! definite assignment assertion operator (while class fields can use both):

    class Foo {
  // These are valid TypeScript
  a?
  b!
  x?() {}

  // This is invalid TypeScript
  y!() {}
}

    Previously esbuild incorrectly allowed the definite assignment assertion operator with class methods. This will no longer be allowed starting with this release.

v0.17.4

Compare Source

  • Implement HTTP HEAD requests in serve mode (#​2851)

    Previously esbuild's serve mode only responded to HTTP GET requests. With this release, esbuild's serve mode will also respond to HTTP HEAD requests, which are just like HTTP GET requests except that the body of the response is omitted.

  • Permit top-level await in dead code branches (#​2853)

    Adding top-level await to a file has a few consequences with esbuild:

    1. It causes esbuild to assume that the input module format is ESM, since top-level await is only syntactically valid in ESM. That prevents you from using module and exports for exports and also enables strict mode, which disables certain syntax and changes how function hoisting works (among other things).
    2. This will cause esbuild to fail the build if either top-level await isn't supported by your language target (e.g. it's not supported in ES2021) or if top-level await isn't supported by the chosen output format (e.g. it's not supported with CommonJS).
    3. Doing this will prevent you from using require() on this file or on any file that imports this file (even indirectly), since the require() function doesn't return a promise and so can't represent top-level await.

    This release relaxes these rules slightly: rules 2 and 3 will now no longer apply when esbuild has identified the code branch as dead code, such as when it's behind an if (false) check. This should make it possible to use esbuild to convert code into different output formats that only uses top-level await conditionally. This release does not relax rule 1. Top-level await will still cause esbuild to unconditionally consider the input module format to be ESM, even when the top-level await is in a dead code branch. This is necessary because whether the input format is ESM or not affects the whole file, not just the dead code branch.

  • Fix entry points where the entire file name is the extension (#​2861)

    Previously if you passed esbuild an entry point where the file extension is the entire file name, esbuild would use the parent directory name to derive the name of the output file. For example, if you passed esbuild a file ./src/.ts then the output name would be src.js. This bug happened because esbuild first strips the file extension to get ./src/ and then joins the path with the working directory to get the absolute path (e.g. join("/working/dir", "./src/") gives /working/dir/src). However, the join operation also canonicalizes the path which strips the trailing /. Later esbuild uses the "base name" operation to extract the name of the output file. Since there is no trailing /, esbuild returns "src" as the base name instead of "", which causes esbuild to incorrectly include the directory name in the output file name. This release fixes this bug by deferring the stripping of the file extension until after all path manipulations have been completed. So now the file ./src/.ts will generate an output file named .js.

  • Support replacing property access expressions with inject

    At a high level, this change means the inject feature can now replace all of the same kinds of names as the define feature. So inject is basically now a more powerful version of define, instead of previously only being able to do some of the things that define could do.

    Soem background is necessary to understand this change if you aren't already familiar with the inject feature. The inject feature lets you replace references to global variable with a shim. It works like this:

    1. Put the shim in its own file
    2. Export the shim as the name of the global variable you intend to replace
    3. Pass the file to esbuild using the inject feature

    For example, if you inject the following file using --inject:./injected.js:

    // injected.js
let processShim = { cwd: () => '/' }
export { processShim as process }

    Then esbuild will replace all references to process with the processShim variable, which will cause process.cwd() to return '/'. This feature is sort of abusing the ESM export alias syntax to specify the mapping of global variables to shims. But esbuild works this way because using this syntax for that purpose is convenient and terse.

    However, if you wanted to replace a property access expression, the process was more complicated and not as nice. You would have to:

    1. Put the shim in its own file
    2. Export the shim as some random name
    3. Pass the file to esbuild using the inject feature
    4. Use esbuild's define feature to map the property access expression to the random name you made in step 2

    For example, if you inject the following file using --inject:./injected2.js --define:process.cwd=someRandomName:

    // injected2.js
let cwdShim = () => '/'
export { cwdShim as someRandomName }

    Then esbuild will replace all references to process.cwd with the cwdShim variable, which will also cause process.cwd() to return '/' (but which this time will not mess with other references to process, which might be desirable).

    With this release, using the inject feature to replace a property access expression is now as simple as using it to replace an identifier. You can now use JavaScript's "arbitrary module namespace identifier names" feature to specify the property access expression directly using a string literal. For example, if you inject the following file using --inject:./injected3.js:

    // injected3.js
let cwdShim = () => '/'
export { cwdShim as 'process.cwd' }

    Then esbuild will now replace all references to process.cwd with the cwdShim variable, which will also cause process.cwd() to return '/' (but which will also not mess with other references to process).

    In addition to inserting a shim for a global variable that doesn't exist, another use case is replacing references to static methods on global objects with cached versions to both minify them better and to make access to them potentially faster. For example:

    // Injected file
let cachedMin = Math.min
let cachedMax = Math.max
export {
  cachedMin as 'Math.min',
  cachedMax as 'Math.max',
}

// Original input
function clampRGB(r, g, b) {
  return {
    r: Math.max(0, Math.min(1, r)),
    g: Math.max(0, Math.min(1, g)),
    b: Math.max(0, Math.min(1, b)),
  }
}

// Old output (with --minify)
function clampRGB(a,t,m){return{r:Math.max(0,Math.min(1,a)),g:Math.max(0,Math.min(1,t)),b:Math.max(0,Math.min(1,m))}}

// New output (with --minify)
var a=Math.min,t=Math.max;function clampRGB(h,M,m){return{r:t(0,a(1,h)),g:t(0,a(1,M)),b:t(0,a(1,m))}}

v0.17.3

Compare Source

  • Fix incorrect CSS minification for certain rules (#​2838)

    Certain rules such as @media could previously be minified incorrectly. Due to a typo in the duplicate rule checker, two known @-rules that share the same hash code were incorrectly considered to be equal. This problem was made worse by the rule hashing code considering two unknown declarations (such as CSS variables) to have the same hash code, which also isn't optimal from a performance perspective. Both of these issues have been fixed:

    /* Original input */
@&#8203;media (prefers-color-scheme: dark) { body { --VAR-1: #&#8203;000; } }
@&#8203;media (prefers-color-scheme: dark) { body { --VAR-2: #&#8203;000; } }

/* Old output (with --minify) */
@&#8203;media (prefers-color-scheme: dark){body{--VAR-2: #&#8203;000}}

/* New output (with --minify) */
@&#8203;media (prefers-color-scheme: dark){body{--VAR-1: #&#8203;000}}@&#8203;media (prefers-color-scheme: dark){body{--VAR-2: #&#8203;000}}

v0.17.2

Compare Source

  • Add onDispose to the plugin API (#​2140, #​2205)

    If your plugin wants to perform some cleanup after it's no longer going to be used, you can now use the onDispose API to register a callback for cleanup-related tasks. For example, if a plugin starts a long-running child process then it may want to terminate that process when the plugin is discarded. Previously there was no way to do this. Here's an example:

    let examplePlugin = {
  name: 'example',
  setup(build) {
    build.onDispose(() => {
      console.log('This plugin is no longer used')
    })
  },
}

    These onDispose callbacks will be called after every build() call regardless of whether the build failed or not as well as after the first dispose() call on a given build context.

v0.17.1

Compare Source

  • Make it possible to cancel a build (#​2725)

    The context object introduced in version 0.17.0 has a new cancel() method. You can use it to cancel a long-running build so that you can start a new one without needing to wait for the previous one to finish. When this happens, the previous build should always have at least one error and have no output files (i.e. it will be a failed build).

    Using it might look something like this:

    • JS:

      let ctx = await esbuild.context({
  // ...
})

let rebuildWithTimeLimit = timeLimit => {
  let timeout = setTimeout(() => ctx.cancel(), timeLimit)
  return ctx.rebuild().finally(() => clearTimeout(timeout))
}

let build = await rebuildWithTimeLimit(500)

    • Go:

      ctx, err := api.Context(api.BuildOptions{
  // ...
})
if err != nil {
  return
}

rebuildWithTimeLimit := func(timeLimit time.Duration) api.BuildResult {
  t := time.NewTimer(timeLimit)
  go func() {
    <-t.C
    ctx.Cancel()
  }()
  result := ctx.Rebuild()
  t.Stop()
  return result
}

build := rebuildWithTimeLimit(500 * time.Millisecond)

    This API is a quick implementation and isn't maximally efficient, so the build may continue to do some work for a little bit before stopping. For example, I have added stop points between each top-level phase of the bundler and in the main module graph traversal loop, but I haven't added fine-grained stop points within the internals of the linker. How quickly esbuild stops can be improved in future releases. This means you'll want to wait for cancel() and/or the previous rebuild() to finish (i.e. await the returned promise in JavaScript) before starting a new build, otherwise rebuild() will give you the just-canceled build that still hasn't ended yet. Note that onEnd callbacks will still be run regardless of whether or not the build was canceled.

  • Fix server-sent events without servedir (#​2827)

    The server-sent events for live reload were incorrectly using servedir to calculate the path to modified output files. This means events couldn't be sent when servedir wasn't specified. This release uses the internal output directory (which is always present) instead of servedir (which might be omitted), so live reload should now work when servedir is not specified.

  • Custom entry point output paths now work with the copy loader (#​2828)

    Entry points can optionally provide custom output paths to change the path of the generated output file. For example, esbuild foo=abc.js bar=xyz.js --outdir=out generates the files out/foo.js and out/bar.js. However, this previously didn't work when using the copy loader due to an oversight. This bug has been fixed. For example, you can now do esbuild foo=abc.html bar=xyz.html --outdir=out --loader:.html=copy to generate the files out/foo.html and out/bar.html.

  • The JS API can now take an array of objects (#​2828)

    Previously it was not possible to specify two entry points with the same custom output path using the JS API, although it was possible to do this with the Go API and the CLI. This will not cause a collision if both entry points use different extensions (e.g. if one uses .js and the other uses .css). You can now pass the JS API an array of obje

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 added the dependencies Pull requests that update a dependency file label Feb 1, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 331816b to 7a4b621 Compare February 1, 2023 02:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7a4b621 to 2b9a1d6 Compare February 1, 2023 07:17
@Codex- Codex- merged commit 9df8bff into main Feb 1, 2023
@Codex- Codex- deleted the renovate/all-minor-patch branch February 1, 2023 07:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Codex-