chore(deps): update all minor dependencies (minor) #4435

renovate · 2023-05-29T02:06:41Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/eslint (source)	`8.37.0` -> `8.40.2`
@types/stylis (source)	`4.0.2` -> `4.2.0`
@unocss/reset	`^0.52.0` -> `^0.53.0`
@vite-pwa/vitepress	`^0.0.5` -> `^0.2.0`
@vueuse/core	`10.1.0` -> `10.2.0`
concurrently	`8.0.1` -> `8.2.0`
cypress	`12.10.0` -> `12.14.0`
cytoscape (source)	`3.23.0` -> `3.25.0`
cytoscape-fcose	`2.1.0` -> `2.2.0`
esbuild	`^0.17.18` -> `^0.18.0`
eslint (source)	`8.39.0` -> `8.43.0`
eslint-plugin-jsdoc	`43.0.7` -> `43.2.0`
pnpm (source)	`8.3.1` -> `8.6.2`
stylis	`4.1.3` -> `4.2.0`
typescript (source)	`5.0.4` -> `5.1.3`
unocss	`^0.52.0` -> `^0.53.0`
unplugin-vue-components	`^0.24.1` -> `^0.25.0`
vite-plugin-pwa	`^0.15.0` -> `^0.16.0`
vue (source)	`3.2.47` -> `3.3.4`
workbox-window (source)	`6.5.4` -> `6.6.0`

Release Notes

unocss/unocss

View changes on GitHub

`v0.53.0`

Compare Source

🚨 Breaking Changes

Normalize extraction content sources - by @antfu and sibbng in https://github.com/unocss/unocss/issues/2719 (3d0c6)
preset-mini: Fix pseudo variants generation order, close #2713 - by @antfu in https://github.com/unocss/unocss/issues/2714 and https://github.com/unocss/unocss/issues/2713 (5c681)

🚀 Features

preset-icons: Fallback on env does not support NodeLoader - by @Fatpandac in https://github.com/unocss/unocss/issues/2693 (4cdac)
preset-mini: Pseudo-class function for custom arguments - by @enpitsuLin in https://github.com/unocss/unocss/issues/2694 (db339)

🐞 Bug Fixes

core:
- Merge theme in mergeConfigs - by @enkot in https://github.com/unocss/unocss/issues/2710 (867fb)
svelte-scoped:
- Use files not folders for exports to fix jiti stub - by @jacob-8 in https://github.com/unocss/unocss/issues/2715 (40a62)
- Global wrap preflights and safelist classes when used in component libraries - by @jacob-8 and @antfu in https://github.com/unocss/unocss/issues/2695 (fe86c)

View changes on GitHub

`v0.52.7`

Compare Source

🚀 Features

svelte-scoped: Add theme() to transform style block pipeline - by @jacob-8 in https://github.com/unocss/unocss/issues/2689 (38487)

🐞 Bug Fixes

transformer-compile-class: Improve duplication checking - by @antfu (4a073)

View changes on GitHub

`v0.52.6`

Compare Source

🚀 Features

preset-mini: Add text-wrap css property - by @mzaien in https://github.com/unocss/unocss/issues/2688 (08962)

🐞 Bug Fixes

transformer-compile-class: Only throw when user explicit name conflicts, close #2667, close #2664 - by @antfu in https://github.com/unocss/unocss/issues/2667 and https://github.com/unocss/unocss/issues/2664 (c54f3)

View changes on GitHub

`v0.52.5`

Compare Source

🐞 Bug Fixes

svelte-scoped:
- Don't add spaces when class names include expressions as just part of them - by @jacob-8 in https://github.com/unocss/unocss/issues/2684 (ee304)
- Properly pass vite command to UnocssSveltePreprocess - by @jacob-8 in https://github.com/unocss/unocss/issues/2685 (fda1c)

View changes on GitHub

`v0.52.4`

Compare Source

🚀 Features

core: Expose mergeConfigs utility - by @antfu (c53d2)
vscode: Ignore config load failed root - by @sapphi-red in https://github.com/unocss/unocss/issues/2662 (071c5)

🐞 Bug Fixes

preset-wind: Key naming in shortcuts from starting with space or divide and not working - by @Dunqing in https://github.com/unocss/unocss/issues/2666 (0c7a7)
vscode: Attributify auto complete - by @sapphi-red in https://github.com/unocss/unocss/issues/2661 (113ba)

View changes on GitHub

`v0.52.3`

Compare Source

🚀 Features

transformer-compile-class: Support for custom class names - by @Techassi and @antfu in https://github.com/unocss/unocss/issues/2577 (ef5db)

🐞 Bug Fixes

astro: The reset style is overwritten - by @Dunqing in https://github.com/unocss/unocss/issues/2656 (e9b15)
cli: Watch cache - by @antfu (a7c3d)
preset-mini: content-none should render { content: none } - by @kcpru and @antfu in https://github.com/unocss/unocss/issues/2650 (636a0)

View changes on GitHub

`v0.52.2`

Compare Source

No significant changes

View changes on GitHub

`v0.52.1`

Compare Source

🐞 Bug Fixes

astro: Incorrect path and build failure - by @Dunqing in https://github.com/unocss/unocss/issues/2648 (1c61f)
preset-attributify: Autocomplete with prefix - by @sapphi-red in https://github.com/unocss/unocss/issues/2643 (83574)
svelte-scoped: @unocss/reset module resolution - by @jacob-8 in https://github.com/unocss/unocss/issues/2644 (153d1)

View changes on GitHub

vite-pwa/vitepress

`v0.2.0`

Compare Source

🚨 Breaking Changes

Bump to vitepress beta 2 - by @userquin in https://github.com/vite-pwa/vitepress/issues/18 (b6e52)

View changes on GitHub

`v0.1.0`

Compare Source

🚨 Breaking Changes

Update vitepress, pwa plugin and workbox to latest - by @userquin (d010d)

🐞 Bug Fixes

Release workflow - by @userquin in https://github.com/vite-pwa/vitepress/issues/16 (d5d62)

View changes on GitHub

vueuse/vueuse

`v10.2.0`

Compare Source

`v10.1.2`

Compare Source

open-cli-tools/concurrently

`v8.2.0`

Compare Source

What's Changed

Support REPL languages that use colons by @wyattades in https://github.com/open-cli-tools/concurrently/pull/393
Update dependencies by @paescuj in https://github.com/open-cli-tools/concurrently/pull/427

New Contributors

@wyattades made their first contribution in https://github.com/open-cli-tools/concurrently/pull/393

Full Changelog: open-cli-tools/concurrently@v8.1.0...v8.2.0

`v8.1.0`

Compare Source

What's Changed

fix: move types condition to the front by @Andarist in https://github.com/open-cli-tools/concurrently/pull/422
Allow setting raw per command when using the API by @chbiel in https://github.com/open-cli-tools/concurrently/pull/411

New Contributors

@Andarist made their first contribution in https://github.com/open-cli-tools/concurrently/pull/422
@chbiel made their first contribution in https://github.com/open-cli-tools/concurrently/pull/411

Full Changelog: open-cli-tools/concurrently@v8.0.1...v8.1.0

cypress-io/cypress

`v12.14.0`

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#12-14-0

`v12.13.0`

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#12-13-0

`v12.12.0`

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#12-12-0

`v12.11.0`

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#12-11-0

cytoscape/cytoscape.js

`v3.25.0`

Compare Source

`v3.24.1`

Compare Source

`v3.24.0`

Compare Source

`v3.23.1`

Compare Source

iVis-at-Bilkent/cytoscape.js-fcose

`v2.2.0`

Compare Source

Adds tiling by sort option
Keeps original location after layout
Fixes a bug on compound nodes with hidden nodes
Fixes a bug related to webpack configuration

evanw/esbuild

`v0.18.4`

Compare Source

Bundling no longer unnecessarily transforms class syntax (#1360, #1328, #1524, #2416)

When bundling, esbuild automatically converts top-level class statements to class expressions. Previously this conversion had the unfortunate side-effect of also transforming certain other class-related syntax features to avoid correctness issues when the references to the class name within the class body. This conversion has been reworked to avoid doing this:
```
// Original code
export class Foo {
  static foo = () => Foo
}

// Old output (with --bundle)
var _Foo = class {
};
var Foo = _Foo;
__publicField(Foo, "foo", () => _Foo);

// New output (with --bundle)
var Foo = class _Foo {
  static foo = () => _Foo;
};
```
This conversion process is very complicated and has many edge cases (including interactions with static fields, static blocks, private class properties, and TypeScript experimental decorators). It should already be pretty robust but a change like this may introduce new unintentional behavior. Please report any issues with this upgrade on the esbuild bug tracker.

You may be wondering why esbuild needs to do this at all. One reason to do this is that esbuild's bundler sometimes needs to lazily-evaluate a module. For example, a module may end up being both the target of a dynamic import() call and a static import statement. Lazy module evaluation is done by wrapping the top-level module code in a closure. To avoid a performance hit for static import statements, esbuild stores top-level exported symbols outside of the closure and references them directly instead of indirectly.

Another reason to do this is that multiple JavaScript VMs have had and continue to have performance issues with TDZ (i.e. "temporal dead zone") checks. These checks validate that a let, or const, or class symbol isn't used before it's initialized. Here are two issues with well-known VMs:
- V8: https://bugs.chromium.org/p/v8/issues/detail?id=13723 (10% slowdown)
- JavaScriptCore: https://bugs.webkit.org/show_bug.cgi?id=199866 (1,000% slowdown!)
JavaScriptCore had a severe performance issue as their TDZ implementation had time complexity that was quadratic in the number of variables needing TDZ checks in the same scope (with the top-level scope typically being the worst offender). V8 has ongoing issues with TDZ checks being present throughout the code their JIT generates even when they have already been checked earlier in the same function or when the function in question has already been run (so the checks have already happened).

Due to esbuild's parallel architecture, esbuild both a) needs to convert class statements into class expressions during parsing and b) doesn't yet know whether this module will need to be lazily-evaluated or not in the parser. So esbuild always does this conversion during bundling in case it's needed for correctness (and also to avoid potentially catastrophic performance issues due to bundling creating a large scope with many TDZ variables).
Enforce TDZ errors in computed class property keys (#2045)

JavaScript allows class property keys to be generated at run-time using code, like this:
```
class Foo {
  static foo = 'foo'
  static [Foo.foo + '2'] = 2
}
```
Previously esbuild treated references to the containing class name within computed property keys as a reference to the partially-initialized class object. That meant code that attempted to reference properties of the class object (such as the code above) would get back undefined instead of throwing an error.

This release rewrites references to the containing class name within computed property keys into code that always throws an error at run-time, which is how this JavaScript code is supposed to work. Code that does this will now also generate a warning. You should never write code like this, but it now should be more obvious when incorrect code like this is written.

Fix an issue with experimental decorators and static fields (#2629)

This release also fixes a bug regarding TypeScript experimental decorators and static class fields which reference the enclosing class name in their initializer. This affected top-level classes when bundling was enabled. Previously code that does this could crash because the class name wasn't initialized yet. This case should now be handled correctly:

// Original code
class Foo {
  @&#8203;someDecorator
  static foo = 'foo'
  static bar = Foo.foo.length
}

// Old output
const _Foo = class {
  static foo = "foo";
  static bar = _Foo.foo.length;
};
let Foo = _Foo;
__decorateClass([
  someDecorator
], Foo, "foo", 2);

// New output
const _Foo = class _Foo {
  static foo = "foo";
  static bar = _Foo.foo.length;
};
__decorateClass([
  someDecorator
], _Foo, "foo", 2);
let Foo = _Foo;

Fix a minification regression with negative numeric properties (#3169)

Version 0.18.0 introduced a regression where computed properties with negative numbers were incorrectly shortened into a non-computed property when minification was enabled. This regression has been fixed:

// Original code
x = {
  [1]: 1,
  [-1]: -1,
  [NaN]: NaN,
  [Infinity]: Infinity,
  [-Infinity]: -Infinity,
}

// Old output (with --minify)
x={1:1,-1:-1,NaN:NaN,1/0:1/0,-1/0:-1/0};

// New output (with --minify)
x={1:1,[-1]:-1,NaN:NaN,[1/0]:1/0,[-1/0]:-1/0};

`v0.18.3`

Compare Source

Fix a panic due to empty static class blocks (#3161)

This release fixes a bug where an internal invariant that was introduced in the previous release was sometimes violated, which then caused a panic. It happened when bundling code containing an empty static class block with both minification and bundling enabled.

`v0.18.2`

Compare Source

Lower static blocks when static fields are lowered (#2800, #2950, #3025)

This release fixes a bug where esbuild incorrectly did not lower static class blocks when static class fields needed to be lowered. For example, the following code should print 1 2 3 but previously printed 2 1 3 instead due to this bug:

// Original code
class Foo {
  static x = console.log(1)
  static { console.log(2) }
  static y = console.log(3)
}

// Old output (with --supported:class-static-field=false)
class Foo {
  static {
    console.log(2);
  }
}
__publicField(Foo, "x", console.log(1));
__publicField(Foo, "y", console.log(3));

// New output (with --supported:class-static-field=false)
class Foo {
}
__publicField(Foo, "x", console.log(1));
console.log(2);
__publicField(Foo, "y", console.log(3));

Use static blocks to implement --keep-names on classes (#2389)

This change fixes a bug where the name property could previously be incorrect within a class static context when using --keep-names. The problem was that the name property was being initialized after static blocks were run instead of before. This has been fixed by moving the name property initializer into a static block at the top of the class body:
```
// Original code
if (typeof Foo === 'undefined') {
  let Foo = class {
    static test = this.name
  }
  console.log(Foo.test)
}

// Old output (with --keep-names)
if (typeof Foo === "undefined") {
  let Foo2 = /* @&#8203;__PURE__ */ __name(class {
    static test = this.name;
  }, "Foo");
  console.log(Foo2.test);
}

// New output (with --keep-names)
if (typeof Foo === "undefined") {
  let Foo2 = class {
    static {
      __name(this, "Foo");
    }
    static test = this.name;
  };
  console.log(Foo2.test);
}
```
This change was somewhat involved, especially regarding what esbuild considers to be side-effect free. Some unused classes that weren't removed by tree shaking in previous versions of esbuild may now be tree-shaken. One example is classes with static private fields that are transformed by esbuild into code that doesn't use JavaScript's private field syntax. Previously esbuild's tree shaking analysis ran on the class after syntax lowering, but with this release it will run on the class before syntax lowering, meaning it should no longer be confused by class mutations resulting from automatically-generated syntax lowering code.

`v0.18.1`

Compare Source

Fill in null entries in input source maps (#3144)

If esbuild bundles input files with source maps and those source maps contain a sourcesContent array with null entries, esbuild previously copied those null entries over to the output source map. With this release, esbuild will now attempt to fill in those null entries by looking for a file on the file system with the corresponding name from the sources array. This matches esbuild's existing behavior that automatically generates the sourcesContent array from the file system if the entire sourcesContent array is missing.
Support /* @__KEY__ */ comments for mangling property names (#2574)

Property mangling is an advanced feature that enables esbuild to minify certain property names, even though it's not possible to automatically determine that it's safe to do so. The safe property names are configured via regular expression such as --mangle-props=_$ (mangle all properties ending in _).

Sometimes it's desirable to also minify strings containing property names, even though it's not possible to automatically determine which strings are property names. This release makes it possible to do this by annotating those strings with /* @__KEY__ */. This is a convention that Terser added earlier this year, and which esbuild is now following too: https://github.com/terser/terser/pull/1365. Using it looks like this:
```
// Original code
console.log(
  [obj.mangle_, obj.keep],
  [obj.get('mangle_'), obj.get('keep')],
  [obj.get(/* @&#8203;__KEY__ */ 'mangle_'), obj.get(/* @&#8203;__KEY__ */ 'keep')],
)

// Old output (with --mangle-props=_$)
console.log(
  [obj.a, obj.keep],
  [obj.get("mangle_"), obj.get("keep")],
  [obj.get(/* @&#8203;__KEY__ */ "mangle_"), obj.get(/* @&#8203;__KEY__ */ "keep")]
);

// New output (with --mangle-props=_$)
console.log(
  [obj.a, obj.keep],
  [obj.get("mangle_"), obj.get("keep")],
  [obj.get(/* @&#8203;__KEY__ */ "a"), obj.get(/* @&#8203;__KEY__ */ "keep")]
);
```
Support /* @__NO_SIDE_EFFECTS__ */ comments for functions (#3149)

Rollup has recently added support for /* @__NO_SIDE_EFFECTS__ */ annotations before functions to indicate that calls to these functions can be removed if the result is unused (i.e. the calls can be assumed to have no side effects). This release adds basic support for these to esbuild as well, which means esbuild will now parse these comments in input files and preserve them in output files. This should help people that use esbuild in combination with Rollup.

Note that this doesn't necessarily mean esbuild will treat these calls as having no side effects, as esbuild's parallel architecture currently isn't set up to enable this type of cross-file tree-shaking information (tree-shaking decisions regarding a function call are currently local to the file they appear in). If you want esbuild to consider a function call to have no side effects, make sure you continue to annotate the function call with /* @__PURE__ */ (which is the previously-established convention for communicating this).

`v0.18.0`

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.17.0 or ~0.17.0. See npm's documentation about semver for more information.

The breaking changes in this release mainly focus on fixing some long-standing issues with esbuild's handling of tsconfig.json files. Here are all the changes in this release, in detail:

Add a way to try esbuild online (#797)

There is now a way to try esbuild live on esbuild's website without installing it: https://esbuild.github.io/try/. In addition to being able to more easily evaluate esbuild, this should also make it more efficient to generate esbuild bug reports. For example, you can use it to compare the behavior of different versions of esbuild on the same input. The state of the page is stored in the URL for easy sharing. Many thanks to @hyrious for creating https://hyrious.me/esbuild-repl/, which was the main inspiration for this addition to esbuild's website.

Two forms of build options are supported: either CLI-style (example) or JS-style (example). Both are converted into a JS object that's passed to esbuild's WebAssembly API. The CLI-style argument parser is a custom one that simulates shell quoting rules, and the JS-style argument parser is also custom and parses a superset of JSON (basically JSON5 + regular expressions). So argument parsing is an approximate simulation of what happens for real but hopefully it should be close enough.
Changes to esbuild's tsconfig.json support (#3019):

This release makes the following changes to esbuild's tsconfig.json support:
- Using experimental decorators now requires "experimentalDecorators": true (#104)
  
  Previously esbuild would always compile decorators in TypeScript code using TypeScript's experimental decorator transform. Now that standard JavaScript decorators are close to being finalized, esbuild will now require you to use "experimentalDecorators": true to do this. This new requirement makes it possible for esbuild to introduce a transform for standard JavaScript decorators in TypeScript code in the future. Such a transform has not been implemented yet, however.
- TypeScript's target no longer affects esbuild's target (#2628)
  
  Some people requested that esbuild support TypeScript's target setting, so support for it was added (in version 0.12.4). However, esbuild supports reading from multiple tsconfig.json files within a single build, which opens up the possibility that different files in the build have different language targets configured. There isn't really any reason to do this and it can lead to unexpected results. So with this release, the target setting in tsconfig.json will no longer affect esbuild's own target setting. You will have to use esbuild's own target setting instead (which is a single, global value).
- TypeScript's jsx setting no longer causes esbuild to preserve JSX syntax (#2634)
  
  TypeScript has a setting called jsx that controls how to transform JSX into JS. The tool-agnostic transform is called react, and the React-specific transform is called react-jsx (or react-jsxdev). There is also a setting called preserve which indicates JSX should be passed through untransformed. Previously people would run esbuild with "jsx": "preserve" in their tsconfig.json files and then be surprised when esbuild preserved their JSX. So with this release, esbuild will now ignore "jsx": "preserve" in tsconfig.json files. If you want to preserve JSX syntax with esbuild, you now have to use --jsx=preserve.
  
  Note: Some people have suggested that esbuild's equivalent jsx setting override the one in tsconfig.json. However, some projects need to legitimately have different files within the same build use different transforms (i.e. react vs. react-jsx) and having esbuild's global jsx setting override tsconfig.json would prevent this from working. This release ignores "jsx": "preserve" but still allows other jsx values in tsconfig.json files to override esbuild's global jsx setting to keep the ability for multiple files within the same build to use different transforms.
- useDefineForClassFields behavior has changed (#2584, #2993)
  
  Class fields in TypeScript look like this (x is a class field):
```
class Foo {
  x = 123
}
```
  TypeScript has legacy behavior that uses assignment semantics instead of define semantics for class fields when useDefineForClassFields is enabled (in which case class fields in TypeScript behave differently than they do in JavaScript, which is arguably "wrong").
  
  This legacy behavior exists because TypeScript added class fields to TypeScript before they were added to JavaScript. The TypeScript team decided to go with assignment semantics and shipped their implementation. Much later on TC39 decided to go with define semantics for class fields in JavaScript instead. This behaves differently if the base class has a setter with the same name:
```
class Base {
  set x(_) {
    console.log('x:', _)
  }
}

// useDefineForClassFields: false
class AssignSemantics extends Base {
  constructor() {
    super()
    this.x = 123
  }
}

// useDefineForClassFields: true
class DefineSemantics extends Base {
  constructor() {
    super()
    Object.defineProperty(this, 'x', { value: 123 })
  }
}

console.log(
  new AssignSemantics().x, // Calls the setter
  new DefineSemantics().x // Doesn't call the setter
)
```
  When you run tsc, the value of useDefineForClassFields defaults to false when it's not specified and the target in tsconfig.json is present but earlier than ES2022. This sort of makes sense because the class field language feature was added in ES2022, so before ES2022 class fields didn't exist (and thus TypeScript's legacy behavior is active). However, TypeScript's target setting currently defaults to ES3 which unfortunately means that the useDefineForClassFields setting currently defaults to false (i.e. to "wrong"). In other words if you run tsc with all default settings, class fields will behave incorrectly.
  
  Previously esbuild tried to do what tsc did. That meant esbuild's version of useDefineForClassFields was false by default, and was also false if esbuild's --target= was present but earlier than es2022. However, TypeScript's legacy class field behavior is becoming increasingly irrelevant and people who expect class fields in TypeScript to work like they do in JavaScript are confused when they use esbuild with default settings. It's also confusing that the behavior of class fields would change if you changed the language target (even though that's exactly how TypeScript works).
  
  So with this release, esbuild will now only use the information in tsconfig.json to determine whether useDefineForClassFields is true or not. Specifically useDefineForClassFields will be respected if present, otherwise it will be false if target is present in tsconfig.json and is ES2021 or earlier, otherwise it will be true. Targets passed to esbuild's --target= setting will no longer affect useDefineForClassFields.
  
  Note that this means different directories in your build can have different values for this setting since esbuild allows different directories to have different tsconfig.json files within the same build. This should let you migrate your code one directory at a time without esbuild's --target= setting affecting the semantics of your code.
- Add support for verbatimModuleSyntax from TypeScript 5.0
  
  TypeScript 5.0 added a new option called verbatimModuleSyntax that deprecates and replaces two older options, preserveValueImports and importsNotUsedAsValues. Setting verbatimModuleSyntax to true in tsconfig.json tells esbuild to not drop unused import statements. Specifically esbuild now treats "verbatimModuleSyntax": true as if you had specified both "preserveValueImports": true and "importsNotUsedAsValues": "preserve".
- Add multiple inheritance for tsconfig.json from TypeScript 5.0
  
  TypeScript 5.0 now allows multiple inheritance for tsconfig.json files. You can now pass an array of filenames via the extends parameter and your tsconfig.json will start off containing properties from all of those configuration files, in order. This release of esbuild adds support for this new TypeScript feature.
- Remove support for moduleSuffixes (#2395)
  
  The community has requested that esbuild remove support for TypeScript's moduleSuffixes feature, so it has been removed in this release. Instead you can use esbuild's --resolve-extensions= feature to select which module suffix you want to build with.
- Apply --tsconfig= overrides to stdin and virtual files (#385, #2543)
  
  When you override esbuild's automatic tsconfig.json file detection with --tsconfig= to pass a specific tsconfig.json file, esbuild previously didn't apply these settings to source code passed via the stdin API option or to TypeScript files from plugins that weren't in the file namespace. This release changes esbuild's behavior so that settings from tsconfig.json also apply to these source code files as well.
- Support --tsconfig-raw= in build API calls (#943, #2440)
  
  Previously if you wanted to override esbuild's automatic tsconfig.json file detection, you had to create a new tsconfig.json file and pass the file name to esbuild via the --tsconfig= flag. With this release, you can now optionally use --tsconfig-raw= instead to pass the contents of tsconfig.json to esbuild directly instead of passing the file name. For example, you can now use --tsconfig-raw={"compilerOptions":{"experimentalDecorators":true}} to enable TypeScript experimental decorators directly using a command-line flag (assuming you escape the quotes correctly using your current shell's quoting rules). The --tsconfig-raw= flag previously only worked with transform API calls but with this release, it now works with build API calls too.
- Ignore all tsconfig.json files in node_modules (#276, #2386)
  
  This changes esbuild's behavior that applies tsconfig.json to all files in the subtree of the directory containing tsconfig.json. In version 0.12.7, esbuild started ignoring tsconfig.json files inside node_modules folders. The rationale is that people typically do this by mistake and that doing this intentionally is a rare use case that doesn't need to be supported. However, this change only applied to certain syntax-specific settings (e.g. jsxFactory) but did not apply to path resolution settings (e.g. paths). With this release, esbuild will now ignore all tsconfig.json files in node_modules instead of only ignoring certain settings.
- Ignore tsconfig.json when resolving paths within node_modules ([#2481](

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

codecov-commenter · 2023-06-17T13:01:22Z

Codecov Report

Merging #4435 (bcf8632) into develop (a76097a) will decrease coverage by 0.04%.
The diff coverage is n/a.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #4435      +/-   ##
===========================================
- Coverage    79.84%   79.81%   -0.04%     
===========================================
  Files          136      136              
  Lines        10446    10446              
  Branches       492      492              
===========================================
- Hits          8341     8337       -4     
+ Misses        1943     1934       -9     
- Partials       162      175      +13

Flag	Coverage Δ
e2e	`79.64% <ø> (-0.07%)`	⬇️
unit	`28.28% <ø> (ø)`

Flags with carried forward coverage won't be shown. Click here to find out more.

see 15 files with indirect coverage changes

[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [mermaid](https://togithub.com/mermaid-js/mermaid) | [`10.2.3` -> `10.2.4`](https://renovatebot.com/diffs/npm/mermaid/10.2.3/10.2.4) | [![age](https://badges.renovateapi.com/packages/npm/mermaid/10.2.4/age-slim)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://badges.renovateapi.com/packages/npm/mermaid/10.2.4/adoption-slim)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://badges.renovateapi.com/packages/npm/mermaid/10.2.4/compatibility-slim/10.2.3)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://badges.renovateapi.com/packages/npm/mermaid/10.2.4/confidence-slim/10.2.3)](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>mermaid-js/mermaid (mermaid)</summary> ### [`v10.2.4`](https://togithub.com/mermaid-js/mermaid/releases/tag/v10.2.4): 10.2.4 [Compare Source](https://togithub.com/mermaid-js/mermaid/compare/v10.2.3...v10.2.4) #### Features - Add Plausible analytics to mermaid.js.org by [@sidharthv96](https://togithub.com/sidharthv96) in [mermaid-js/mermaid#4473 - Support for development in Docker by [@nirname](https://togithub.com/nirname) in [mermaid-js/mermaid#4478 - standardize info diagram definitions by [@Yokozuna59](https://togithub.com/Yokozuna59) in [mermaid-js/mermaid#4486 - Change C4 stereotype braces from ASCII <\</>> to Unicode «/» by [@jonathan-r-young](https://togithub.com/jonathan-r-young) in [mermaid-js/mermaid#4460 - Add coverage for E2E tests by [@sidharthv96](https://togithub.com/sidharthv96) in [mermaid-js/mermaid#4498 - set normal mode for vitest coverage by [@Yokozuna59](https://togithub.com/Yokozuna59) in [mermaid-js/mermaid#4505 - Use v8 coverage in vitest by [@sidharthv96](https://togithub.com/sidharthv96) in [mermaid-js/mermaid#4560 - feat(flowchart): add classDef style group definition by [@tomperr](https://togithub.com/tomperr) in [mermaid-js/mermaid#3923 - add cypress coverage clean by [@Yokozuna59](https://togithub.com/Yokozuna59) in [mermaid-js/mermaid#4556 - fix(class): keep members in namespace classes by [@tomperr](https://togithub.com/tomperr) in [mermaid-js/mermaid#4532 #### Bugfixes - Add hint on "flowchart" and "graph" by [@koppor](https://togithub.com/koppor) in [mermaid-js/mermaid#4096 - fix(flowchart): apply style on doublecircle by [@tomperr](https://togithub.com/tomperr) in [mermaid-js/mermaid#4540 - fix not rendered style when style is optional by [@Yokozuna59](https://togithub.com/Yokozuna59) in [mermaid-js/mermaid#4528 - fix(flowchart): allow multiple vertices with style by [@tomperr](https://togithub.com/tomperr) in [mermaid-js/mermaid#4553 #### Documentation - change REAMDME.md coverage from coveralls into codecov by [@Yokozuna59](https://togithub.com/Yokozuna59) in [mermaid-js/mermaid#4507 - Update latest news section by [@huynhicode](https://togithub.com/huynhicode) in [mermaid-js/mermaid#4468 - Fix link to Tutorials from n00b-overview page by [@Spiderpig86](https://togithub.com/Spiderpig86) in [mermaid-js/mermaid#4472 - Fix Directives Documentation by [@adamazing](https://togithub.com/adamazing) in [mermaid-js/mermaid#4475 - Correct "Bronze" spelling in timeline docs by [@adamazing](https://togithub.com/adamazing) in [mermaid-js/mermaid#4467 - Document recommended file extension and MIME type docs by [@bollwyvl](https://togithub.com/bollwyvl) in [mermaid-js/mermaid#4485 - Fix typo in quadrant chart documentation by [@tobie](https://togithub.com/tobie) in [mermaid-js/mermaid#4512 - fix cspell issues in \*.md files by [@Yokozuna59](https://togithub.com/Yokozuna59) in [mermaid-js/mermaid#4531 - docs: Howto on foreground color on timelines by [@mcbeelen](https://togithub.com/mcbeelen) in [mermaid-js/mermaid#4524 - Add citation.cff file by [@schackartk](https://togithub.com/schackartk) in [mermaid-js/mermaid#4521 - Update Tutorials.md by [@ellenealds](https://togithub.com/ellenealds) in [mermaid-js/mermaid#4539 - Add Standard Notes extension in integrations page by [@nienow](https://togithub.com/nienow) in [mermaid-js/mermaid#4557 - Fix up Gantt Chart demo by [@AlexMooney](https://togithub.com/AlexMooney) in [mermaid-js/mermaid#4561 #### Chore - Update all patch dependencies (patch) by [@renovate](https://togithub.com/renovate) in [mermaid-js/mermaid#4482 - chore: revise Contributing documentation by [@weedySeaDragon](https://togithub.com/weedySeaDragon) in [mermaid-js/mermaid#3814 - chore(deps): update all minor dependencies (minor) by [@renovate](https://togithub.com/renovate) in [mermaid-js/mermaid#4435 - fix(deps): update all patch dependencies (patch) by [@renovate](https://togithub.com/renovate) in [mermaid-js/mermaid#4510 - fix(deps): update all patch dependencies (patch) by [@renovate](https://togithub.com/renovate) in [mermaid-js/mermaid#4535 - chore(deps): update dependency eslint-plugin-jsdoc to v46 by [@renovate](https://togithub.com/renovate) in [mermaid-js/mermaid#4544 - chore(deps): update dependency jsdom to v22 by [@renovate](https://togithub.com/renovate) in [mermaid-js/mermaid#4546 - chore(deps): update dependency eslint-plugin-unicorn to v47 by [@renovate](https://togithub.com/renovate) in [mermaid-js/mermaid#4545 - chore(deps): update dependency workbox-window to v7 by [@renovate](https://togithub.com/renovate) in [mermaid-js/mermaid#4547 - chore(deps): update node.js to v20 by [@renovate](https://togithub.com/renovate) in [mermaid-js/mermaid#4548 - fix(deps): update all patch dependencies (patch) by [@renovate](https://togithub.com/renovate) in [mermaid-js/mermaid#4543 - add `Suggested Solutions` field in `bug_report.yml` by [@Yokozuna59](https://togithub.com/Yokozuna59) in [mermaid-js/mermaid#4541 #### New Contributors - [@Spiderpig86](https://togithub.com/Spiderpig86) made their first contribution in [mermaid-js/mermaid#4472 - [@adamazing](https://togithub.com/adamazing) made their first contribution in [mermaid-js/mermaid#4475 - [@koppor](https://togithub.com/koppor) made their first contribution in [mermaid-js/mermaid#4096 - [@nirname](https://togithub.com/nirname) made their first contribution in [mermaid-js/mermaid#4478 - [@Yokozuna59](https://togithub.com/Yokozuna59) made their first contribution in [mermaid-js/mermaid#4486 - [@jonathan-r-young](https://togithub.com/jonathan-r-young) made their first contribution in [mermaid-js/mermaid#4460 - [@tobie](https://togithub.com/tobie) made their first contribution in [mermaid-js/mermaid#4512 - [@schackartk](https://togithub.com/schackartk) made their first contribution in [mermaid-js/mermaid#4521 - [@mcbeelen](https://togithub.com/mcbeelen) made their first contribution in [mermaid-js/mermaid#4524 - [@ellenealds](https://togithub.com/ellenealds) made their first contribution in [mermaid-js/mermaid#4539 - [@nienow](https://togithub.com/nienow) made their first contribution in [mermaid-js/mermaid#4557 - [@AlexMooney](https://togithub.com/AlexMooney) made their first contribution in [mermaid-js/mermaid#4561 **Full Changelog**: mermaid-js/mermaid@v10.2.3...v10.2.4 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), 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. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/levaintech/contented).  Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

renovate bot force-pushed the renovate/all-minor branch 3 times, most recently from 37a02c4 to e7d3c4a Compare May 31, 2023 11:07

renovate bot force-pushed the renovate/all-minor branch 7 times, most recently from 31985f7 to 179125f Compare June 8, 2023 06:17

renovate bot changed the title ~~chore(deps): update all minor dependencies (minor)~~ Update all minor dependencies (minor) Jun 8, 2023

renovate bot force-pushed the renovate/all-minor branch 19 times, most recently from 06d12c5 to 25347ff Compare June 15, 2023 05:05

renovate bot force-pushed the renovate/all-minor branch 9 times, most recently from 04e87ba to e73375c Compare June 17, 2023 11:20

renovate bot changed the title ~~Update all minor dependencies (minor)~~ chore(deps): update all minor dependencies (minor) Jun 17, 2023

renovate bot force-pushed the renovate/all-minor branch 3 times, most recently from 372946e to 52276a0 Compare June 17, 2023 12:57

renovate bot force-pushed the renovate/all-minor branch from 52276a0 to 51a0a4a Compare June 17, 2023 17:54

chore(deps): update all minor dependencies

bcf8632

renovate bot force-pushed the renovate/all-minor branch from 51a0a4a to bcf8632 Compare June 17, 2023 21:30

renovate bot merged commit 2ee3775 into develop Jun 18, 2023

renovate bot deleted the renovate/all-minor branch June 18, 2023 06:35

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update all minor dependencies (minor) #4435

chore(deps): update all minor dependencies (minor) #4435

renovate bot commented May 29, 2023 •

edited

Loading

codecov-commenter commented Jun 17, 2023 •

edited

Loading

chore(deps): update all minor dependencies (minor) #4435

chore(deps): update all minor dependencies (minor) #4435

Conversation

renovate bot commented May 29, 2023 • edited Loading

Release Notes

🚀 Features

🐞 Bug Fixes

🚨 Breaking Changes

🚀 Features

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

🐞 Bug Fixes

🚨 Breaking Changes

🚨 Breaking Changes

🐞 Bug Fixes

What's Changed

New Contributors

What's Changed

New Contributors

Configuration

codecov-commenter commented Jun 17, 2023 • edited Loading

Codecov Report

renovate bot commented May 29, 2023 •

edited

Loading

codecov-commenter commented Jun 17, 2023 •

edited

Loading