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 #35

Merged
merged 1 commit into from
Aug 26, 2023
Merged

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

merged 1 commit into from
Aug 26, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 26, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 20.3.1 -> 20.5.6 age adoption passing confidence
esbuild 0.19.0 -> 0.19.2 age adoption passing confidence
eslint (source) 8.46.0 -> 8.48.0 age adoption passing confidence
netlify-cli 15.10.0 -> 15.11.0 age adoption passing confidence
pnpm (source) 8.6.12 -> 8.7.0 age adoption passing confidence
prettier (source) 3.0.1 -> 3.0.2 age adoption passing confidence

Release Notes

evanw/esbuild (esbuild)

v0.19.2

Compare Source

  • Update how CSS nesting is parsed again

    CSS nesting syntax has been changed again, and esbuild has been updated to match. Type selectors may now be used with CSS nesting:

    .foo {
  div {
    color: red;
  }
}

    Previously this was disallowed in the CSS specification because it's ambiguous whether an identifier is a declaration or a nested rule starting with a type selector without requiring unbounded lookahead in the parser. It has now been allowed because the CSS working group has decided that requiring unbounded lookahead is acceptable after all.

    Note that this change means esbuild no longer considers any existing browser to support CSS nesting since none of the existing browsers support this new syntax. CSS nesting will now always be transformed when targeting a browser. This situation will change in the future as browsers add support for this new syntax.

  • Fix a scope-related bug with --drop-labels= (#​3311)

    The recently-released --drop-labels= feature previously had a bug where esbuild's internal scope stack wasn't being restored properly when a statement with a label was dropped. This could manifest as a tree-shaking issue, although it's possible that this could have also been causing other subtle problems too. The bug has been fixed in this release.

  • Make renamed CSS names unique across entry points (#​3295)

    Previously esbuild's generated names for local names in CSS were only unique within a given entry point (or across all entry points when code splitting was enabled). That meant that building multiple entry points with esbuild could result in local names being renamed to the same identifier even when those entry points were built simultaneously within a single esbuild API call. This problem was especially likely to happen with minification enabled. With this release, esbuild will now avoid renaming local names from two separate entry points to the same name if those entry points were built with a single esbuild API call, even when code splitting is disabled.

  • Fix CSS ordering bug with @layer before @import

    CSS lets you put @layer rules before @import rules to define the order of layers in a stylesheet. Previously esbuild's CSS bundler incorrectly ordered these after the imported files because before the introduction of cascade layers to CSS, imported files could be bundled by removing the @import rules and then joining files together in the right order. But with @layer, CSS files may now need to be split apart into multiple pieces in the bundle. For example:

    /* Original code */
@​layer start;
@​import "data:text/css,@​layer inner.start;";
@​import "data:text/css,@​layer inner.end;";
@​layer end;

/* Old output (with --bundle) */
@​layer inner.start;
@​layer inner.end;
@​layer start;
@​layer end;

/* New output (with --bundle) */
@​layer start;
@​layer inner.start;
@​layer inner.end;
@​layer end;

  • Unwrap nested duplicate @media rules (#​3226)

    With this release, esbuild's CSS minifier will now automatically unwrap duplicate nested @media rules:

    /* Original code */
@​media (min-width: 1024px) {
  .foo { color: red }
  @​media (min-width: 1024px) {
    .bar { color: blue }
  }
}

/* Old output (with --minify) */
@​media (min-width: 1024px){.foo{color:red}@​media (min-width: 1024px){.bar{color:#​00f}}}

/* New output (with --minify) */
@​media (min-width: 1024px){.foo{color:red}.bar{color:#​00f}}

    These rules are unlikely to be authored manually but may result from using frameworks such as Tailwind to generate CSS.

v0.19.1

Compare Source

  • Fix a regression with baseURL in tsconfig.json (#​3307)

    The previous release moved tsconfig.json path resolution before --packages=external checks to allow the paths field in tsconfig.json to avoid a package being marked as external. However, that reordering accidentally broke the behavior of the baseURL field from tsconfig.json. This release moves these path resolution rules around again in an attempt to allow both of these cases to work.

  • Parse TypeScript type arguments for JavaScript decorators (#​3308)

    When parsing JavaScript decorators in TypeScript (i.e. with experimentalDecorators disabled), esbuild previously didn't parse type arguments. Type arguments will now be parsed starting with this release. For example:

    @&#8203;foo<number>
@&#8203;bar<number, string>()
class Foo {}

  • Fix glob patterns matching extra stuff at the end (#​3306)

    Previously glob patterns such as ./*.js would incorrectly behave like ./*.js* during path matching (also matching .js.map files, for example). This was never intentional behavior, and has now been fixed.

  • Change the permissions of esbuild's generated output files (#​3285)

    This release changes the permissions of the output files that esbuild generates to align with the default behavior of node's fs.writeFileSync function. Since most tools written in JavaScript use fs.writeFileSync, this should make esbuild more consistent with how other JavaScript build tools behave.

    The full Unix-y details: Unix permissions use three-digit octal notation where the three digits mean "user, group, other" in that order. Within a digit, 4 means "read" and 2 means "write" and 1 means "execute". So 6 == 4 + 2 == read + write. Previously esbuild uses 0644 permissions (the leading 0 means octal notation) but the permissions for fs.writeFileSync defaults to 0666, so esbuild will now use 0666 permissions. This does not necessarily mean that the files esbuild generates will end up having 0666 permissions, however, as there is another Unix feature called "umask" where the operating system masks out some of these bits. If your umask is set to 0022 then the generated files will have 0644 permissions, and if your umask is set to 0002 then the generated files will have 0664 permissions.

  • Fix a subtle CSS ordering issue with @import and @layer

    With this release, esbuild may now introduce additional @layer rules when bundling CSS to better preserve the layer ordering of the input code. Here's an example of an edge case where this matters:

    /* entry.css */
@&#8203;import "a.css";
@&#8203;import "b.css";
@&#8203;import "a.css";
    /* a.css */
@&#8203;layer a {
  body {
    background: red;
  }
}
    /* b.css */
@&#8203;layer b {
  body {
    background: green;
  }
}

    This CSS should set the body background to green, which is what happens in the browser. Previously esbuild generated the following output which incorrectly sets the body background to red:

    /* b.css */
@&#8203;layer b {
  body {
    background: green;
  }
}

/* a.css */
@&#8203;layer a {
  body {
    background: red;
  }
}

    This difference in behavior is because the browser evaluates a.css + b.css + a.css (in CSS, each @import is replaced with a copy of the imported file) while esbuild was only writing out b.css + a.css. The first copy of a.css wasn't being written out by esbuild for two reasons: 1) bundlers care about code size and try to avoid emitting duplicate CSS and 2) when there are multiple copies of a CSS file, normally only the last copy matters since the last declaration with equal specificity wins in CSS.

    However, @layer was recently added to CSS and for @layer the first copy matters because layers are ordered using their first location in source code order. This introduction of @layer means esbuild needs to change its bundling algorithm. An easy solution would be for esbuild to write out a.css twice, but that would be inefficient. So what I'm going to try to have esbuild do with this release is to write out an abbreviated form of the first copy of a CSS file that only includes the @layer information, and then still only write out the full CSS file once for the last copy. So esbuild's output for this edge case now looks like this:

    /* a.css */
@&#8203;layer a;

/* b.css */
@&#8203;layer b {
  body {
    background: green;
  }
}

/* a.css */
@&#8203;layer a {
  body {
    background: red;
  }
}

    The behavior of the bundled CSS now matches the behavior of the unbundled CSS. You may be wondering why esbuild doesn't just write out a.css first followed by b.css. That would work in this case but it doesn't work in general because for any rules outside of a @layer rule, the last copy should still win instead of the first copy.

  • Fix a bug with esbuild's TypeScript type definitions (#​3299)

    This release fixes a copy/paste error with the TypeScript type definitions for esbuild's JS API:

     export interface TsconfigRaw {
   compilerOptions?: {
-    baseUrl?: boolean
+    baseUrl?: string
     ...
   }
 }

    This fix was contributed by @​privatenumber.

eslint/eslint (eslint)

v8.48.0

Compare Source

Features

  • 1fbb3b0 feat: correct update direction in for-direction (#​17483) (Francesco Trotta)
  • d73fbf2 feat: rule tester do not create empty valid or invalid test suites (#​17475) (fnx)
  • ee2f718 feat: Allow void in rule no-promise-executor-return (#​17282) (nopeless)

Bug Fixes

  • 7234f6a fix: update RuleTester JSDoc and deprecations (#​17496) (Jonas Berlin)

Documentation

  • 7a51d77 docs: no-param-reassign mention strict mode (#​17494) (Stephen Hardy)
  • 9cd7ac2 docs: add fetch script to package.json conventions (#​17459) (Nitin Kumar)
  • cab21e6 docs: advice for inline disabling of rules (#​17458) (Ashish Yadav)
  • 056499d docs: fix example of flat config from plugin (#​17482) (Francesco Trotta)
  • 9e9edf9 docs: update documentation URL in error message (#​17465) (Nitin Kumar)

Chores

v8.47.0

Compare Source

Features
  • 53d7508 feat: update regex for methods with thisArg (#​17439) (Francesco Trotta)
Bug Fixes
  • 631648e fix: do not report on shadowed constructors in no-new-wrappers (#​17447) (Francesco Trotta)
Documentation
Chores
netlify/cli (netlify-cli)

v15.11.0

Compare Source

Features
pnpm/pnpm (pnpm)

v8.7.0

Compare Source

Minor Changes
  • Improve performance of installation by using a worker pool for extracting packages and writing them to the content-addressable store #​6850
  • The default value of the resolution-mode setting is changed to highest. This setting was changed to lowest-direct in v8.0.0 and some users were not happy with the change. A twitter poll concluded that most of the users want the old behaviour (resolution-mode set to highest by default). This is a semi-breaking change but should not affect users that commit their lockfile #​6463.
Patch Changes
  • Warn when linking a package with peerDependencies #​615.
  • Add support for npm lockfile v3 in pnpm import #​6233.
  • Override peerDependencies in pnpm.overrides #​6759.
  • Respect workspace alias syntax in pkg graph #​6922
  • Emit a clear error message when users attempt to specify an undownloadable node version #​6916.
  • pnpm patch should write patch files with a trailing newline #​6905.
  • Dedupe deps with the same alias in direct dependencies 6966
  • Don't prefix install output for the dlx command.
  • Performance optimizations. Package tarballs are now download directly to memory and built to an ArrayBuffer. Hashing and other operations are avoided until the stream has been fully received #​6819.
Our Gold Sponsors
Our Silver Sponsors
prettier/prettier (prettier)

v3.0.2

Compare Source

diff

Break after = of assignment if RHS is poorly breakable AwaitExpression or YieldExpression (#​15204 by @​seiyab)
// Input
const { section, rubric, authors, tags } = await utils.upsertCommonData(mainData);

// Prettier 3.0.1
const { section, rubric, authors, tags } = await utils.upsertCommonData(
  mainData,
);

// Prettier 3.0.2
const { section, rubric, authors, tags } =
  await utils.upsertCommonData(mainData);
Do not add trailing comma for grouped scss comments (#​15217 by @​auvred)
/* Input */
$foo: (
	'property': (),
	// comment 1
	// comment 2
)

/* Prettier 3.0.1 */
$foo: (
  "property": (),
  // comment 1
  // comment 2,
);

/* Prettier 3.0.2 */
$foo: (
  "property": (),
  // comment 1
  // comment 2
);
Print declare and export keywords for nested namespace (#​15249 by @​sosukesuzuki)
// Input
declare namespace abc1.def {}
export namespace abc2.def {}

// Prettier 3.0.1
namespace abc1.def {}
namespace abc2.def {}

// Prettier 3.0.2
declare namespace abc1.def {}
export namespace abc2.def {}

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 merged commit a15541b into main Aug 26, 2023
6 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch August 26, 2023 23:25
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.
0 participants