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 all non-major dependencies #96

Merged

aAmorim27 merged 1 commit into main from renovate/all-minor-patch

Apr 13, 2023

Contributor

renovate bot commented Mar 20, 2023 •

edited

Loading

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@commitlint/cli (source)	`^17.4.4` -> `^17.5.1`					devDependencies	minor
@headlessui/vue	`^1.7.12` -> `^1.7.13`					dependencies	patch
@pnpm/find-workspace-packages (source)	`^6.0.4` -> `^6.0.5`					devDependencies	patch
@pnpm/find-workspace-packages (source)	`^6.0.4` -> `^6.0.5`					dependencies	patch
@popperjs/core	`^2.11.6` -> `^2.11.7`					dependencies	patch
@rollup/plugin-commonjs (source)	`^24.0.1` -> `^24.1.0`					dependencies	minor
@rollup/plugin-node-resolve (source)	`^15.0.1` -> `^15.0.2`					dependencies	patch
@types/lodash (source)	`^4.14.191` -> `^4.14.192`					devDependencies	patch
@types/lodash-es (source)	`^4.17.6` -> `^4.17.7`					devDependencies	patch
@types/node (source)	`^18.15.3` -> `^18.15.11`					devDependencies	patch
@typescript-eslint/eslint-plugin	`5.55.0` -> `5.58.0`					devDependencies	minor
@typescript-eslint/parser	`5.55.0` -> `5.58.0`					devDependencies	minor
@vitejs/plugin-vue (source)	`^4.0.0` -> `^4.1.0`					devDependencies	minor
@vitejs/plugin-vue (source)	`^4.0.0` -> `^4.1.0`					dependencies	minor
@vue/test-utils	`^2.3.1` -> `^2.3.2`					devDependencies	patch
chromatic (source)	`^6.17.1` -> `^6.17.3`					devDependencies	patch
esbuild	`^0.17.11` -> `^0.17.16`					dependencies	patch
eslint (source)	`^8.36.0` -> `^8.38.0`					devDependencies	minor
eslint-config-prettier	`8.7.0` -> `8.8.0`					devDependencies	minor
eslint-define-config	`^1.16.0` -> `^1.17.0`					devDependencies	minor
eslint-plugin-vue (source)	`9.9.0` -> `9.10.0`					devDependencies	minor
fs-extra	`^11.1.0` -> `^11.1.1`					dependencies	patch
lint-staged	`^13.2.0` -> `^13.2.1`					devDependencies	patch
node	`>= v18.15.0` -> `>= v18.16.0`					engines	minor
pnpm (source)	`8.1.1` -> `8.2.0`					packageManager	minor
prettier (source)	`^2.8.4` -> `^2.8.7`					devDependencies	patch
rimraf	`^4.4.0` -> `^4.4.1`					devDependencies	patch
rollup (source)	`^3.19.1` -> `^3.20.2`					dependencies	minor
sass	`^1.59.2` -> `^1.62.0`					devDependencies	minor
tailwindcss (source)	`^3.2.7` -> `^3.3.1`					devDependencies	minor
tsx	`^3.12.5` -> `^3.12.6`					devDependencies	patch
unbuild	`^1.1.2` -> `^1.2.0`					devDependencies	minor
unplugin-vue-define-options (source)	`^1.2.4` -> `^1.3.3`					devDependencies	minor
unplugin-vue-define-options (source)	`^1.2.4` -> `^1.3.3`					dependencies	minor
vite (source)	`^4.1.4` -> `^4.2.1`					devDependencies	minor
vitest	`^0.29.2` -> `^0.30.1`					devDependencies	minor

Release Notes

conventional-changelog/commitlint

`v17.5.1`

Note: Version bump only for package @commitlint/cli

`v17.5.0`

Note: Version bump only for package @commitlint/cli

17.4.4 (2023-02-17)

Note: Version bump only for package @commitlint/cli

17.4.3 (2023-02-13)

Note: Version bump only for package @commitlint/cli

17.4.2 (2023-01-12)

Note: Version bump only for package @commitlint/cli

17.4.1 (2023-01-09)

Note: Version bump only for package @commitlint/cli

tailwindlabs/headlessui

`v1.7.13`

Fixed

Fix focus styles showing up when using the mouse (#2347)
Disable ComboboxInput when its Combobox is disabled (#2375)
Add FocusTrap event listeners once document has loaded (#2389)
Don't scroll-lock <Dialog> when wrapping transition isn't showing (#2422)
Ensure DOM ref is properly handled in the RadioGroup component (#2424)

Added

Add form prop to form-like components such as RadioGroup, Switch, Listbox, and Combobox (#2356)

popperjs/popper-core

`v2.11.7`: @popperjs/core@2.11.7

Bug Fixes

fix: Use correct window to get the devicePixelRatio #2229

rollup/plugins (@rollup/plugin-commonjs)

`v24.1.0`

2023-04-11

Features

feat: Do not use getters for module.exports #1455

rollup/plugins (@rollup/plugin-node-resolve)

`v15.0.2`

2023-04-04

Bugfixes

fix: bump is-builtin-module version, imports with a trailing slash #1424

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

`v5.58.0`

Bug Fixes

eslint-plugin: [unified-signatures] allow overloads with different named and different number of parameters (#6877) (939d665)

Features

eslint-plugin: [no-unsafe-enum-comparison] add rule (#6107) (915f9c2)

5.57.1 (2023-04-03)

Bug Fixes

eslint-plugin: [strict-boolean-expressions] support mixed enums in allowNullableEnum option (#6740) (49be8a8)

`v5.57.1`

Bug Fixes

eslint-plugin: [strict-boolean-expressions] support mixed enums in allowNullableEnum option (#6740) (49be8a8)

`v5.57.0`

Bug Fixes

eslint-plugin: [no-unnecessary-boolean-literal-compare] simplify fixer and add support for double negation (#6620) (81c8519)
eslint-plugin: correct crashes with getTypeArguments for ts < 3.7 (#6767) (59eab58)

Features

eslint-plugin: [consistent-type-assertions] add suggestions for objectLiteralTypeAssertions (#6642) (720e811)
eslint-plugin: [consistent-type-assertions] autofix angle bracket assertions to as (#6641) (ad8ea64)
eslint-plugin: add no-duplicate-type-constituents rule (#5728) (bc31078)

`v5.56.0`

Bug Fixes

eslint-plugin: [member-ordering] check order when optionalityOrder is present with no optional members (#6619) (6aff431)
eslint-plugin: [no-misused-promises] avoid unnecessary calls to getContextualType (#6193) (745cfe4)
eslint-plugin: [no-misused-promises] fix incorrect detection of void functions in JSX attributes (#6638) (9e41cee)
eslint-plugin: [strict-boolean-expression] support falsy and truthy literals simultaneously (#6672) (62ef487)
eslint-plugin: [strict-boolean-expressions] handle truthy enums (#6618) (0d0639f)
eslint-plugin: add TSPropertySignature with TSFunctionType annotation to typeMethod selector (#6645) (3fc5c63)

Features

eslint-plugin: add allowNever support to restrict-template-expressions (#6554) (423f164)

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

`v5.58.0`

Bug Fixes

update getLib for new TypeScript targets ES2021, ES2022 (#6782) (1c04664)

5.57.1 (2023-04-03)

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

`v5.57.1`

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

`v5.57.0`

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

`v5.56.0`

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

vitejs/vite-plugin-vue

`v4.1.0`

fix: avoid resolving to 2.7 compiler-sfc (cf36b3e)

vuejs/test-utils

`v2.3.2`

What's Changed

fix propsData deprecation suggestion by @dten in https://github.com/vuejs/test-utils/pull/2001
chore(deps): update all non-major dependencies by @renovate in https://github.com/vuejs/test-utils/pull/2006
chore(deps): update vitest to v0.29.3 by @renovate in https://github.com/vuejs/test-utils/pull/2007
docs: add ssr page to navigation by @freakzlike in https://github.com/vuejs/test-utils/pull/2011
chore: export ComponentMountingOptions to resolve type definetions in testing script by user by @jason-chang in https://github.com/vuejs/test-utils/pull/2009

New Contributors

@dten made their first contribution in https://github.com/vuejs/test-utils/pull/2001
@jason-chang made their first contribution in https://github.com/vuejs/test-utils/pull/2009

Full Changelog: vuejs/test-utils@v2.3.1...v2.3.2

chromaui/chromatic-cli

`v6.17.3`

`v6.17.2`

726 Increase timeout on Storybook Verification
725 Bump webpack from 5.72.1 to 5.76.0
711 Bump http-cache-semantics from 4.1.0 to 4.1.1

evanw/esbuild

`v0.17.16`

Fix CSS nesting transform for triple-nested rules that start with a combinator (#3046)

This release fixes a bug with esbuild where triple-nested CSS rules that start with a combinator were not transformed correctly for older browsers. Here's an example of such a case before and after this bug fix:

/* Original input */
.a {
  color: red;
  > .b {
    color: green;
    > .c {
      color: blue;
    }
  }
}

/* Old output (with --target=chrome90) */
.a {
  color: red;
}
.a > .b {
  color: green;
}
.a .b > .c {
  color: blue;
}

/* New output (with --target=chrome90) */
.a {
  color: red;
}
.a > .b {
  color: green;
}
.a > .b > .c {
  color: blue;
}

Support --inject with a file loaded using the copy loader (#3041)

This release now allows you to use --inject with a file that is loaded using the copy loader. The copy loader copies the imported file to the output directory verbatim and rewrites the path in the import statement to point to the copied output file. When used with --inject, this means the injected file will be copied to the output directory as-is and a bare import statement for that file will be inserted in any non-copy output files that esbuild generates.

Note that since esbuild doesn't parse the contents of copied files, esbuild will not expose any of the export names as usable imports when you do this (in the way that esbuild's --inject feature is typically used). However, any side-effects that the injected file has will still occur.

`v0.17.15`

Allow keywords as type parameter names in mapped types (#3033)

TypeScript allows type keywords to be used as parameter names in mapped types. Previously esbuild incorrectly treated this as an error. Code that does this is now supported:
```
type Foo = 'a' | 'b' | 'c'
type A = { [keyof in Foo]: number }
type B = { [infer in Foo]: number }
type C = { [readonly in Foo]: number }
```
Add annotations for re-exported modules in node (#2486, #3029)

Node lets you import named imports from a CommonJS module using ESM import syntax. However, the allowed names aren't derived from the properties of the CommonJS module. Instead they are derived from an arbitrary syntax-only analysis of the CommonJS module's JavaScript AST.

To accommodate node doing this, esbuild's ESM-to-CommonJS conversion adds a special non-executable "annotation" for node that describes the exports that node should expose in this scenario. It takes the form 0 && (module.exports = { ... }) and comes at the end of the file (0 && expr means expr is never evaluated).

Previously esbuild didn't do this for modules re-exported using the export * from syntax. Annotations for these re-exports will now be added starting with this release:
```
// Original input
export { foo } from './foo'
export * from './bar'

// Old output (with --format=cjs --platform=node)
...
0 && (module.exports = {
  foo
});

// New output (with --format=cjs --platform=node)
...
0 && (module.exports = {
  foo,
  ...require("./bar")
});
```
Note that you need to specify both --format=cjs and --platform=node to get these node-specific annotations.
Avoid printing an unnecessary space in between a number and a . (#3026)

JavaScript typically requires a space in between a number token and a . token to avoid the . being interpreted as a decimal point instead of a member expression. However, this space is not required if the number token itself contains a decimal point, an exponent, or uses a base other than 10. This release of esbuild now avoids printing the unnecessary space in these cases:
```
// Original input
foo(1000 .x, 0 .x, 0.1 .x, 0.0001 .x, 0xFFFF_0000_FFFF_0000 .x)

// Old output (with --minify)
foo(1e3 .x,0 .x,.1 .x,1e-4 .x,0xffff0000ffff0000 .x);

// New output (with --minify)
foo(1e3.x,0 .x,.1.x,1e-4.x,0xffff0000ffff0000.x);
```
Fix server-sent events with live reload when writing to the file system root (#3027)

This release fixes a bug where esbuild previously failed to emit server-sent events for live reload when outdir was the file system root, such as /. This happened because / is the only path on Unix that cannot have a trailing slash trimmed from it, which was fixed by improved path handling.

`v0.17.14`

Allow the TypeScript 5.0 const modifier in object type declarations (#3021)

The new TypeScript 5.0 const modifier was added to esbuild in version 0.17.5, and works with classes, functions, and arrow expressions. However, support for it wasn't added to object type declarations (e.g. interfaces) due to an oversight. This release adds support for these cases, so the following TypeScript 5.0 code can now be built with esbuild:
```
interface Foo { <const T>(): T }
type Bar = { new <const T>(): T }
```
Implement preliminary lowering for CSS nesting (#1945)

Chrome has implemented the new CSS nesting specification in version 112, which is currently in beta but will become stable very soon. So CSS nesting is now a part of the web platform!

This release of esbuild can now transform nested CSS syntax into non-nested CSS syntax for older browsers. The transformation relies on the :is() pseudo-class in many cases, so the transformation is only guaranteed to work when targeting browsers that support :is() (e.g. Chrome 88+). You'll need to set esbuild's target to the browsers you intend to support to tell esbuild to do this transformation. You will get a warning if you use CSS nesting syntax with a target which includes older browsers that don't support :is().

The lowering transformation looks like this:
```
/* Original input */
a.btn {
  color: #&#8203;333;
  &:hover { color: #&#8203;444 }
  &:active { color: #&#8203;555 }
}

/* New output (with --target=chrome88) */
a.btn {
  color: #&#8203;333;
}
a.btn:hover {
  color: #&#8203;444;
}
a.btn:active {
  color: #&#8203;555;
}
```
More complex cases may generate the :is() pseudo-class:
```
/* Original input */
div, p {
  .warning, .error {
    padding: 20px;
  }
}

/* New output (with --target=chrome88) */
:is(div, p) :is(.warning, .error) {
  padding: 20px;
}
```
In addition, esbuild now has a special warning message for nested style rules that start with an identifier. This isn't allowed in CSS because the syntax would be ambiguous with the existing declaration syntax. The new warning message looks like this:
```
▲ [WARNING] A nested style rule cannot start with "p" because it looks like the start of a declaration [css-syntax-error]

    <stdin>:1:7:
      1 │ main { p { margin: auto } }
        │        ^
        ╵        :is(p)

  To start a nested style rule with an identifier, you need to wrap the identifier in ":is(...)" to
  prevent the rule from being parsed as a declaration.
```
Keep in mind that the transformation in this release is a preliminary implementation. CSS has many features that interact in complex ways, and there may be some edge cases that don't work correctly yet.

Minification now removes unnecessary & CSS nesting selectors

This release introduces the following CSS minification optimizations:

/* Original input */
a {
  font-weight: bold;
  & {
    color: blue;
  }
  & :hover {
    text-decoration: underline;
  }
}

/* Old output (with --minify) */
a{font-weight:700;&{color:#&#8203;00f}& :hover{text-decoration:underline}}

/* New output (with --minify) */
a{font-weight:700;:hover{text-decoration:underline}color:#&#8203;00f}

Minification now removes duplicates from CSS selector lists

This release introduces the following CSS minification optimization:

/* Original input */
div, div { color: red }

/* Old output (with --minify) */
div,div{color:red}

/* New output (with --minify) */
div{color:red}

`v0.17.13`

Work around an issue with NODE_PATH and Go's WebAssembly internals (#3001)

Go's WebAssembly implementation returns EINVAL instead of ENOTDIR when using the readdir syscall on a file. This messes up esbuild's implementation of node's module resolution algorithm since encountering ENOTDIR causes esbuild to continue its search (since it's a normal condition) while other encountering other errors causes esbuild to fail with an I/O error (since it's an unexpected condition). You can encounter this issue in practice if you use node's legacy NODE_PATH feature to tell esbuild to resolve node modules in a custom directory that was not installed by npm. This release works around this problem by converting EINVAL into ENOTDIR for the readdir syscall.
Fix a minification bug with CSS @layer rules that have parsing errors (#3016)

CSS at-rules require either a {} block or a semicolon at the end. Omitting both of these causes esbuild to treat the rule as an unknown at-rule. Previous releases of esbuild had a bug that incorrectly removed unknown at-rules without any children during minification if the at-rule token matched an at-rule that esbuild can handle. Specifically cssnano can generate @layer rules with parsing errors, and empty @layer rules cannot be removed because they have side effects (@layer didn't exist when esbuild's CSS support was added, so esbuild wasn't written to handle this). This release changes esbuild to no longer discard @layer rules with parsing errors when minifying (the rule @layer c has a parsing error):
```
/* Original input */
@&#8203;layer a {
  @&#8203;layer b {
    @&#8203;layer c
  }
}

/* Old output (with --minify) */
@&#8203;layer a.b;

/* New output (with --minify) */
@&#8203;layer a.b.c;
```
Unterminated strings in CSS are no longer an error

The CSS specification provides rules for handling parsing errors. One of those rules is that user agents must close strings upon reaching the end of a line (i.e., before an unescaped line feed, carriage return or form feed character), but then drop the construct (declaration or rule) in which the string was found. For example:
```
p {
  color: green;
  font-family: 'Courier New Times
  color: red;
  color: green;
}
```
...would be treated the same as:
```
p { color: green; color: green; }
```
...because the second declaration (from font-family to the semicolon after color: red) is invalid and is dropped.

Previously using this CSS with esbuild failed to build due to a syntax error, even though the code can be interpreted by a browser. With this release, the code now produces a warning instead of an error, and esbuild prints the invalid CSS such that it stays invalid in the output:
```
/* esbuild's new non-minified output: */
p {
  color: green;
  font-family: 'Courier New Times
  color: red;
  color: green;
}
```
```
/* esbuild's new minified output: */
p{font-family:'Courier New Times
color: red;color:green}
```

`v0.17.12`

Fix a crash when parsing inline TypeScript decorators (#2991)

Previously esbuild's TypeScript parser crashed when parsing TypeScript decorators if the definition of the decorator was inlined into the decorator itself:
```
@&#8203;(function sealed(c
```

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (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 bot added the dependencies label

renovate bot force-pushed the renovate/all-minor-patch branch 21 times, most recently from df6c87f to 2f9d501 Compare

March 26, 2023 05:32

renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from a71ccf1 to accfaea Compare

March 31, 2023 13:49

renovate bot force-pushed the renovate/all-minor-patch branch 12 times, most recently from 1ce127c to 8dcdbcf Compare

April 8, 2023 01:07

renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 77332be to 4f3fa68 Compare

April 12, 2023 21:12


          chore(deps): update all non-major dependencies

af9cb3e

renovate bot force-pushed the renovate/all-minor-patch branch from 4f3fa68 to af9cb3e Compare

April 13, 2023 01:50

aAmorim27 approved these changes

View reviewed changes

aAmorim27 merged commit abb7a3e into main

aAmorim27 deleted the renovate/all-minor-patch branch

April 13, 2023 07:42

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels