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

Merged
merged 1 commit into from
Feb 7, 2024
Merged

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

merged 1 commit into from
Feb 7, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 27, 2024 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) ^20.11.5 -> ^20.11.16 age adoption passing confidence
@vitest/coverage-v8 (source) ^1.2.1 -> ^1.2.2 age adoption passing confidence
esbuild ^0.19.11 -> ^0.20.0 age adoption passing confidence
pnpm (source) 8.14.1 -> 8.15.1 age adoption passing confidence
postcss (source) ^8.4.33 -> ^8.4.34 age adoption passing confidence
prettier (source) ^3.2.4 -> ^3.2.5 age adoption passing confidence
sass ^1.69.7 -> ^1.70.0 age adoption passing confidence
vitest (source) ^1.2.1 -> ^1.2.2 age adoption passing confidence
vue (source) ^3.3.4 -> ^3.4.15 age adoption passing confidence
vue-tsc (source) ^1.8.5 -> ^1.8.27 age adoption passing confidence
vue-tsc (source) ^1.8.5 -> ^1.8.27 age adoption passing confidence

Release Notes

vitest-dev/vitest (@​vitest/coverage-v8)

v1.2.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
evanw/esbuild (esbuild)

v0.20.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.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

  • Work around API deprecations in Deno 1.40.x (#​3609, #​3611)

    Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

    Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

  • Reorder implicit file extensions within node_modules (#​3341, #​3608)

    In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

    With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

    Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.

v0.19.12

Compare Source

  • The "preserve" JSX mode now preserves JSX text verbatim (#​3605)

    The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).

    Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:

    // Original code
let el =
  <a href={'/'} title='&apos;&quot;'> some text
    {foo}
      more text </a>

// Old output (with --loader=jsx --jsx=preserve)
let el = <a href="/" title={`'"`}>
  {" some text"}
  {foo}
  {"more text "}
</a>;

// New output (with --loader=jsx --jsx=preserve)
let el = <a href={"/"} title='&apos;&quot;'> some text
    {foo}
      more text </a>;

  • Allow JSX elements as JSX attribute values

    JSX has an obscure feature where you can use JSX elements in attribute position without surrounding them with {...}. It looks like this:

    let el = <div data-ab=<><a/><b/></>/>;

    I think I originally didn't implement it even though it's part of the JSX specification because it previously didn't work in TypeScript (and potentially also in Babel?). However, support for it was silently added in TypeScript 4.8 without me noticing and Babel has also since fixed their bugs regarding this feature. So I'm adding it to esbuild too now that I know it's widely supported.

    Keep in mind that there is some ongoing discussion about removing this feature from JSX. I agree that the syntax seems out of place (it does away with the elegance of "JSX is basically just XML with {...} escapes" for something arguably harder to read, which doesn't seem like a good trade-off), but it's in the specification and TypeScript and Babel both implement it so I'm going to have esbuild implement it too. However, I reserve the right to remove it from esbuild if it's ever removed from the specification in the future. So use it with caution.

  • Fix a bug with TypeScript type parsing (#​3574)

    This release fixes a bug with esbuild's TypeScript parser where a conditional type containing a union type that ends with an infer type that ends with a constraint could fail to parse. This was caused by the "don't parse a conditional type" flag not getting passed through the union type parser. Here's an example of valid TypeScript code that previously failed to parse correctly:

    type InferUnion<T> = T extends { a: infer U extends number } | infer U extends number ? U : never
pnpm/pnpm (pnpm)

v8.15.1

Compare Source

Patch Changes

  • Use the object-hash library instead of node-object-hash for hashing keys of side-effects cache #​7591.
  • bundledDependencies should never be added to the lockfile with false as the value #​7576.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.0

Compare Source

Minor Changes

  • When the license field does not exist in package.json but a license file exists, try to match and extract the license name #​7530.

Patch Changes

  • Running pnpm update -r --latest will no longer downgrade prerelease dependencies #​7436.
  • --aggregate-output should work on scripts executed from the same project #​7556.
  • Prefer hard links over reflinks on Windows as they perform better #​7564.
  • Reduce the length of the side-effects cache key. Instead of saving a stringified object composed from the dependency versions of the package, use the hash calculated from the said object #​7563.
  • Throw an error if pnpm update --latest runs with arguments containing versions specs. For instance, pnpm update --latest foo@next is not allowed #​7567.
  • Don't fail in Windows CoW if the file already exists #​7554.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.14.3

Compare Source

Patch Changes

  • pnpm pack should work as expected when "prepack" modifies the manifest #​7558.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.14.2

Compare Source

Patch Changes

  • Registry configuration from previous installation should not override current settings #​7507.
  • pnpm dlx should not fail, when executed from package.json "scripts" 7424.
  • A git-hosted dependency should not be added to the store if it failed to be built #​7407.
  • pnpm publish should pack "main" file or "bin" files defined in "publishConfig" #​4195.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors
postcss/postcss (postcss)

v8.4.34

Compare Source

  • Fixed AtRule#nodes type (by Tim Weißenfels).
  • Cleaned up code (by Dmitry Kirillov).
prettier/prettier (prettier)

v3.2.5

Compare Source

diff

Support Angular inline styles as single template literal (#​15968 by @​sosukesuzuki)

Angular v17 supports single string inline styles.

// Input
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.4
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.5
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `
    h1 {
      color: blue;
    }
  `,
})
export class AppComponent {}
Unexpected embedded formatting for Angular template (#​15969 by @​JounQin)

Computed template should not be considered as Angular component template

// Input
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.4
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{ hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.5
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}
Use "json" parser for tsconfig.json by default (#​16012 by @​sosukesuzuki)

In v2.3.0, we introduced "jsonc" parser which adds trialing comma by default.

When adding a new parser we also define how it will be used based on the linguist-languages data.

tsconfig.json is a special file used by TypeScript, it uses .json file extension, but it actually uses the JSON with Comments syntax. However, we found that there are many third-party tools not recognize it correctly because of the confusing .json file extension.

We decide to treat it as a JSON file for now to avoid the extra configuration step.

To keep using the "jsonc" parser for your tsconfig.json files, add the following to your .pretterrc file

{
  "overrides": [
    {
      "files": ["tsconfig.json", "jsconfig.json"],
      "options": {
        "parser": "jsonc"
      }
    }
  ]
}
sass/dart-sass (sass)

v1.70.0

Compare Source

JavaScript API

  • Add a sass.initCompiler() function that returns a sass.Compiler object
    which supports compile() and compileString() methods with the same API as
    the global Sass object. On the Node.js embedded host, each sass.Compiler
    object uses a single long-lived subprocess, making compiling multiple
    stylesheets much more efficient.

  • Add a sass.initAsyncCompiler() function that returns a sass.AsyncCompiler
    object which supports compileAsync() and compileStringAsync() methods with
    the same API as the global Sass object. On the Node.js embedded host, each
    sass.AsynCompiler object uses a single long-lived subprocess, making
    compiling multiple stylesheets much more efficient.

Embedded Sass

  • Support the CompileRequest.silent field. This allows compilations with no
    logging to avoid unnecessary request/response cycles.

  • The Dart Sass embedded compiler now reports its name as "dart-sass" rather
    than "Dart Sass", to match the JS API's info field.

vuejs/language-tools (vue-tsc)

v1.8.27

Compare Source

v1.8.26

Compare Source

v1.8.25

Compare Source

  • fix(component-type-helpers): correct type inference for FunctionalComponent (#​3766) - thanks @​pinguet62
  • fix(language-core): camelize props for dynamic component (#​3774) - thanks @​so1ve

v1.8.24

Compare Source

  • refactor(component-type-helpers): vue 2 types now move to vue-component-type-helpers/vue2 (#​3404)
  • feat(language-core): expose defineEmits's arg and typeArg in parseScriptSetupRanges (#​3710) - thanks @​so1ve
  • fix(language-core): strictTemplates fails to report unknown components (#​3539)
  • fix(language-core): script syntax breaks if script options does not have trailing comma (#​3755)
  • fix(language-core): script syntax breaks if options are enclosed in parentheses (#​3756)
  • fix(language-core): allow using as with multiple <script> blocks (#​3733) - thanks @​so1ve
  • fix(language-core): component type narrowing not working in template
  • fix(language-core): incremental insertion incorrect if input <script setup> tag above <script> tag (#​3743) - thanks @​so1ve
  • fix(language-core): don't camelize attributes for plain elements (#​3750) - thanks @​rchl
  • fix(vscode): syntax highlighting for .prop shorthand (#​3729) - thanks @​so1ve
Volar.js 1.11.1 updates:

v1.8.22

Compare Source

  • fix: experimentalResolveStyleCssClasses: "always" not working (#​3689) - thanks @​maIIady
  • fix: __VLS_Prettify missing for dts build when uses withDefaults() (#​3691)

v1.8.21

Compare Source

Volar.js 1.10.5 updates:

v1.8.20

[Compare Source](https://to

Configuration

📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).

🚦 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.

@codecov Codecov
Copy link

codecov bot commented Jan 27, 2024 •
edited

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (b7c396d) 82.86% compared to head (faa7a86) 82.86%.

❗ Current head faa7a86 differs from pull request most recent head a2dbd02. Consider uploading reports for the commit a2dbd02 to get more accurate results

Additional details and impacted files 
@@           Coverage Diff           @@
##             main     #195   +/-   ##
=======================================
  Coverage   82.86%   82.86%           
=======================================
  Files          12       12           
  Lines         852      852           
  Branches      133      133           
=======================================
  Hits          706      706           
  Misses        144      144           
  Partials        2        2

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 3429d10 to 065b34b Compare February 1, 2024 19:18
@renovate renovate bot merged commit 3532fe2 into main Feb 7, 2024
2 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch February 7, 2024 01:26
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
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants