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

Update Dev Dependencies #157

Merged
merged 1 commit into from
Nov 27, 2023
Merged

Update Dev Dependencies #157

merged 1 commit into from
Nov 27, 2023

Conversation

mend-for-github-com[bot]
Copy link
Contributor

@mend-for-github-com mend-for-github-com bot commented Nov 1, 2023 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
@types/tape (source) devDependencies patch 5.6.1 -> 5.6.4
esbuild devDependencies patch 0.19.4 -> 0.19.8
eslint (source) devDependencies minor 8.50.0 -> 8.54.0
eslint-plugin-import devDependencies minor 2.28.1 -> 2.29.0
tape devDependencies patch 5.7.0 -> 5.7.2

Release Notes

evanw/esbuild

v0.19.8

Compare Source

  • Add a treemap chart to esbuild's bundle analyzer (#​2848)

    The bundler analyzer on esbuild's website (https://esbuild.github.io/analyze/) now has a treemap chart type in addition to the two existing chart types (sunburst and flame). This should be more familiar for people coming from other similar tools, as well as make better use of large screens.

  • Allow decorators after the export keyword (#​104)

    Previously esbuild's decorator parser followed the original behavior of TypeScript's experimental decorators feature, which only allowed decorators to come before the export keyword. However, the upcoming JavaScript decorators feature also allows decorators to come after the export keyword. And with TypeScript 5.0, TypeScript now also allows experimental decorators to come after the export keyword too. So esbuild now allows this as well:

    // This old syntax has always been permitted:
@​decorator export class Foo {}
@​decorator export default class Foo {}

// This new syntax is now permitted too:
export @​decorator class Foo {}
export default @​decorator class Foo {}

    In addition, esbuild's decorator parser has been rewritten to fix several subtle and likely unimportant edge cases with esbuild's parsing of exports and decorators in TypeScript (e.g. TypeScript apparently does automatic semicolon insertion after interface and export interface but not after export default interface).

  • Pretty-print decorators using the same whitespace as the original

    When printing code containing decorators, esbuild will now try to respect whether the original code contained newlines after the decorator or not. This can make generated code containing many decorators much more compact to read:

    // Original code
class Foo {
  @​a @​b @​c abc
  @​x @​y @​z xyz
}

// Old output
class Foo {
  @​a
  @​b
  @​c
  abc;
  @​x
  @​y
  @​z
  xyz;
}

// New output
class Foo {
  @​a @​b @​c abc;
  @​x @​y @​z xyz;
}

v0.19.7

Compare Source

  • Add support for bundling code that uses import attributes (#​3384)

    JavaScript is gaining new syntax for associating a map of string key-value pairs with individual ESM imports. The proposal is still a work in progress and is still undergoing significant changes before being finalized. However, the first iteration has already been shipping in Chromium-based browsers for a while, and the second iteration has landed in V8 and is now shipping in node, so it makes sense for esbuild to support it. Here are the two major iterations of this proposal (so far):

    1. Import assertions (deprecated, will not be standardized)

      • Uses the assert keyword
      • Does not affect module resolution
      • Causes an error if the assertion fails
      • Shipping in Chrome 91+ (and in esbuild 0.11.22+)

    2. Import attributes (currently set to become standardized)

      • Uses the with keyword
      • Affects module resolution
      • Unknown attributes cause an error
      • Shipping in node 21+

    You can already use esbuild to bundle code that uses import assertions (the first iteration). However, this feature is mostly useless for bundlers because import assertions are not allowed to affect module resolution. It's basically only useful as an annotation on external imports, which esbuild will then preserve in the output for use in a browser (which would otherwise refuse to load certain imports).

    With this release, esbuild now supports bundling code that uses import attributes (the second iteration). This is much more useful for bundlers because they are allowed to affect module resolution, which means the key-value pairs can be provided to plugins. Here's an example, which uses esbuild's built-in support for the upcoming JSON module standard:

    // On static imports
import foo from './package.json' with { type: 'json' }
console.log(foo)

// On dynamic imports
const bar = await import('./package.json', { with: { type: 'json' } })
console.log(bar)

    One important consequence of the change in semantics between import assertions and import attributes is that two imports with identical paths but different import attributes are now considered to be different modules. This is because the import attributes are provided to the loader, which might then use those attributes during loading. For example, you could imagine an image loader that produces an image of a different size depending on the import attributes.

    Import attributes are now reported in the metafile and are now provided to on-load plugins as a map in the with property. For example, here's an esbuild plugin that turns all imports with a type import attribute equal to 'cheese' into a module that exports the cheese emoji:

    const cheesePlugin = {
  name: 'cheese',
  setup(build) {
    build.onLoad({ filter: /.*/ }, args => {
      if (args.with.type === 'cheese') return {
        contents: `export default "🧀"`,
      }
    })
  }
}

require('esbuild').build({
  bundle: true,
  write: false,
  stdin: {
    contents: `
      import foo from 'data:text/javascript,' with { type: 'cheese' }
      console.log(foo)
    `,
  },
  plugins: [cheesePlugin],
}).then(result => {
  const code = new Function(result.outputFiles[0].text)
  code()
})

    Warning: It's possible that the second iteration of this feature may change significantly again even though it's already shipping in real JavaScript VMs (since it has already happened once before). In that case, esbuild may end up adjusting its implementation to match the eventual standard behavior. So keep in mind that by using this, you are using an unstable upcoming JavaScript feature that may undergo breaking changes in the future.

  • Adjust TypeScript experimental decorator behavior (#​3230, #​3326, #​3394)

    With this release, esbuild will now allow TypeScript experimental decorators to access both static class properties and #private class names. For example:

    const check =
  <T,>(a: T, b: T): PropertyDecorator =>
    () => console.log(a === b)

async function test() {
  class Foo {
    static #foo = 1
    static bar = 1 + Foo.#foo
    @&#8203;check(Foo.#foo, 1) a: any
    @&#8203;check(Foo.bar, await Promise.resolve(2)) b: any
  }
}

test().then(() => console.log('pass'))

    This will now print true true pass when compiled by esbuild. Previously esbuild evaluated TypeScript decorators outside of the class body, so it didn't allow decorators to access Foo or #foo. Now esbuild does something different, although it's hard to concisely explain exactly what esbuild is doing now (see the background section below for more information).

    Note that TypeScript's experimental decorator support is currently buggy: TypeScript's compiler passes this test if only the first @check is present or if only the second @check is present, but TypeScript's compiler fails this test if both checks are present together. I haven't changed esbuild to match TypeScript's behavior exactly here because I'm waiting for TypeScript to fix these bugs instead.

    Some background: TypeScript experimental decorators don't have consistent semantics regarding the context that the decorators are evaluated in. For example, TypeScript will let you use await within a decorator, which implies that the decorator runs outside the class body (since await isn't supported inside a class body), but TypeScript will also let you use #private names, which implies that the decorator runs inside the class body (since #private names are only supported inside a class body). The value of this in a decorator is also buggy (the run-time value of this changes if any decorator in the class uses a #private name but the type of this doesn't change, leading to the type checker no longer matching reality). These inconsistent semantics make it hard for esbuild to implement this feature as decorator evaluation happens in some superposition of both inside and outside the class body that is particular to the internal implementation details of the TypeScript compiler.

  • Forbid --keep-names when targeting old browsers (#​3477)

    The --keep-names setting needs to be able to assign to the name property on functions and classes. However, before ES6 this property was non-configurable, and attempting to assign to it would throw an error. So with this release, esbuild will no longer allow you to enable this setting while also targeting a really old browser.

v0.19.6

Compare Source

  • Fix a constant folding bug with bigint equality

    This release fixes a bug where esbuild incorrectly checked for bigint equality by checking the equality of the bigint literal text. This is correct if the bigint doesn't have a radix because bigint literals without a radix are always in canonical form (since leading zeros are not allowed). However, this is incorrect if the bigint has a radix (e.g. 0x123n) because the canonical form is not enforced when a radix is present.

    // Original code
console.log(!!0n, !!1n, 123n === 123n)
console.log(!!0x0n, !!0x1n, 123n === 0x7Bn)

// Old output
console.log(false, true, true);
console.log(true, true, false);

// New output
console.log(false, true, true);
console.log(!!0x0n, !!0x1n, 123n === 0x7Bn);

  • Add some improvements to the JavaScript minifier

    This release adds more cases to the JavaScript minifier, including support for inlining String.fromCharCode and String.prototype.charCodeAt when possible:

    // Original code
document.onkeydown = e => e.keyCode === 'A'.charCodeAt(0) && console.log(String.fromCharCode(55358, 56768))

// Old output (with --minify)
document.onkeydown=o=>o.keyCode==="A".charCodeAt(0)&&console.log(String.fromCharCode(55358,56768));

// New output (with --minify)
document.onkeydown=o=>o.keyCode===65&&console.log("🧀");

    In addition, immediately-invoked function expressions (IIFEs) that return a single expression are now inlined when minifying. This makes it possible to use IIFEs in combination with @__PURE__ annotations to annotate arbitrary expressions as side-effect free without the IIFE wrapper impacting code size. For example:

    // Original code
const sideEffectFreeOffset = /* @&#8203;__PURE__ */ (() => computeSomething())()
use(sideEffectFreeOffset)

// Old output (with --minify)
const e=(()=>computeSomething())();use(e);

// New output (with --minify)
const e=computeSomething();use(e);

  • Automatically prefix the mask-composite CSS property for WebKit (#​3493)

    The mask-composite property will now be prefixed as -webkit-mask-composite for older WebKit-based browsers. In addition to prefixing the property name, handling older browsers also requires rewriting the values since WebKit uses non-standard names for the mask composite modes:

    /* Original code */
div {
  mask-composite: add, subtract, intersect, exclude;
}

/* New output (with --target=chrome100) */
div {
  -webkit-mask-composite:
    source-over,
    source-out,
    source-in,
    xor;
  mask-composite:
    add,
    subtract,
    intersect,
    exclude;
}

  • Avoid referencing this from JSX elements in derived class constructors (#​3454)

    When you enable --jsx=automatic and --jsx-dev, the JSX transform is supposed to insert this as the last argument to the jsxDEV function. I'm not sure exactly why this is and I can't find any specification for it, but in any case this causes the generated code to crash when you use a JSX element in a derived class constructor before the call to super() as this is not allowed to be accessed at that point. For example

    // Original code
class ChildComponent extends ParentComponent {
  constructor() {
    super(<div />)
  }
}

// Problematic output (with --loader=jsx --jsx=automatic --jsx-dev)
import { jsxDEV } from "react/jsx-dev-runtime";
class ChildComponent extends ParentComponent {
  constructor() {
    super(/* @&#8203;__PURE__ */ jsxDEV("div", {}, void 0, false, {
      fileName: "<stdin>",
      lineNumber: 3,
      columnNumber: 15
    }, this)); // The reference to "this" crashes here
  }
}

    The TypeScript compiler doesn't handle this at all while the Babel compiler just omits this for the entire constructor (even after the call to super()). There seems to be no specification so I can't be sure that this change doesn't break anything important. But given that Babel is pretty loose with this and TypeScript doesn't handle this at all, I'm guessing this value isn't too important. React's blog post seems to indicate that this value was intended to be used for a React-specific migration warning at some point, so it could even be that this value is irrelevant now. Anyway the crash in this case should now be fixed.

  • Allow package subpath imports to map to node built-ins (#​3485)

    You are now able to use a subpath import in your package to resolve to a node built-in module. For example, with a package.json file like this:

    {
  "type": "module",
  "imports": {
    "#stream": {
      "node": "stream",
      "default": "./stub.js"
    }
  }
}

    You can now import from node's stream module like this:

    import * as stream from '#stream';
console.log(Object.keys(stream));

    This will import from node's stream module when the platform is node and from ./stub.js otherwise.

  • No longer throw an error when a Symbol is missing (#​3453)

    Certain JavaScript syntax features use special properties on the global Symbol object. For example, the asynchronous iteration syntax uses Symbol.asyncIterator. Previously esbuild's generated code for older browsers required this symbol to be polyfilled. However, starting with this release esbuild will use Symbol.for() to construct these symbols if they are missing instead of throwing an error about a missing polyfill. This means your code no longer needs to include a polyfill for missing symbols as long as your code also uses Symbol.for() for missing symbols.

  • Parse upcoming changes to TypeScript syntax (#​3490, #​3491)

    With this release, you can now use from as the name of a default type-only import in TypeScript code, as well as of as the name of an await using loop iteration variable:

    import type from from 'from'
for (await using of of of) ;

    This matches similar changes in the TypeScript compiler (#​56376 and #​55555) which will start allowing this syntax in an upcoming version of TypeScript. Please never actually write code like this.

    The type-only import syntax change was contributed by @​magic-akari.

v0.19.5

Compare Source

  • Fix a regression in 0.19.0 regarding paths in tsconfig.json (#​3354)

    The fix in esbuild version 0.19.0 to process tsconfig.json aliases before the --packages=external setting unintentionally broke an edge case in esbuild's handling of certain tsconfig.json aliases where there are multiple files with the same name in different directories. This release adjusts esbuild's behavior for this edge case so that it passes while still processing aliases before --packages=external. Please read the linked issue for more details.

  • Fix a CSS font property minification bug (#​3452)

    This release fixes a bug where esbuild's CSS minifier didn't insert a space between the font size and the font family in the font CSS shorthand property in the edge case where the original source code didn't already have a space and the leading string token was shortened to an identifier:

    /* Original code */
.foo { font: 16px"Menlo"; }

/* Old output (with --minify) */
.foo{font:16pxMenlo}

/* New output (with --minify) */
.foo{font:16px Menlo}

  • Fix bundling CSS with asset names containing spaces (#​3410)

    Assets referenced via CSS url() tokens may cause esbuild to generate invalid output when bundling if the file name contains spaces (e.g. url(image 2.png)). With this release, esbuild will now quote all bundled asset references in url() tokens to avoid this problem. This only affects assets loaded using the file and copy loaders.

  • Fix invalid CSS url() tokens in @import rules (#​3426)

    In the future, CSS url() tokens may contain additional stuff after the URL. This is irrelevant today as no CSS specification does this. But esbuild previously had a bug where using these tokens in an @import rule resulted in malformed output. This bug has been fixed.

  • Fix browser + false + type: module in package.json (#​3367)

    The browser field in package.json allows you to map a file to false to have it be treated as an empty file when bundling for the browser. However, if package.json contains "type": "module" then all .js files will be considered ESM, not CommonJS. Importing a named import from an empty CommonJS file gives you undefined, but importing a named export from an empty ESM file is a build error. This release changes esbuild's interpretation of these files mapped to false in this situation from ESM to CommonJS to avoid generating build errors for named imports.

  • Fix a bug in top-level await error reporting (#​3400)

    Using require() on a file that contains top-level await is not allowed because require() must return synchronously and top-level await makes that impossible. You will get a build error if you try to bundle code that does this with esbuild. This release fixes a bug in esbuild's error reporting code for complex cases of this situation involving multiple levels of imports to get to the module containing the top-level await.

  • Update to Unicode 15.1.0

    The character tables that determine which characters form valid JavaScript identifiers have been updated from Unicode version 15.0.0 to the newly-released Unicode version 15.1.0. I'm not putting an example in the release notes because all of the new characters will likely just show up as little squares since fonts haven't been updated yet. But you can read https://www.unicode.org/versions/Unicode15.1.0/#Summary for more information about the changes.

    This upgrade was contributed by @​JLHwung.

eslint/eslint

v8.54.0

Compare Source

Features

  • a7a883b feat: for-direction rule add check for condition in reverse order (#​17755) (Angelo Annunziata)
  • 1452dc9 feat: Add suggestions to no-console (#​17680) (Joel Mathew Koshy)
  • 21ebf8a feat: update no-array-constructor rule (#​17711) (Francesco Trotta)

Bug Fixes

  • 98926e6 fix: Ensure that extra data is not accidentally stored in the cache file (#​17760) (Milos Djermanovic)
  • e8cf9f6 fix: Make dark scroll bar in dark theme (#​17753) (Pavel)
  • 3cbeaad fix: Use cwd constructor option as config basePath in Linter (#​17705) (Milos Djermanovic)

Documentation

  • becfdd3 docs: Make clear when rules are removed (#​17728) (Nicholas C. Zakas)
  • 05d6e99 docs: update "Submit a Pull Request" page (#​17712) (Francesco Trotta)
  • eb2279e docs: display info about deprecated rules (#​17749) (Percy Ma)
  • d245326 docs: Correct working in migrating plugin docs (#​17722) (Filip Tammergård)

Chores

v8.53.0

Compare Source

Features

  • 528e1c0 feat: Deprecate formatting rules (#​17696) (Nicholas C. Zakas)
  • c0b11dd feat: Add suggestions for no-prototype-builtins (#​17677) (Yonathan Randolph)

Bug Fixes

  • 1ad6257 fix: ensure that exit code for fatal errors is not overwritten (#​17683) (Milos Djermanovic)
  • b329ea7 fix: add ; after JSX nodes in no-object-constructor autofix (#​17672) (Francesco Trotta)

Documentation

  • ab8c60d docs: change position of return to top button (#​17688) (Tanuj Kanti)
  • 4fc44c0 docs: update twitter icon to new X icon (#​17687) (Tanuj Kanti)
  • 4164b2c docs: Update README (GitHub Actions Bot)
  • 8651895 docs: Fix tabs in rule examples (#​17653) (Francesco Trotta)
  • 3aec1c5 docs: explained rule fixers and suggestions (#​17657) (Josh Goldberg ✨)

Chores

v8.52.0

Compare Source

Features

  • 70648ee feat: report-unused-disable-directive to report unused eslint-enable (#​17611) (Yosuke Ota)

Bug Fixes

  • 5de9637 fix: Ensure shared references in rule configs are separated (#​17666) (Nicholas C. Zakas)
  • dcfe573 fix: add preceding semicolon in suggestions of no-object-constructor (#​17649) (Francesco Trotta)

Documentation

  • 476d58a docs: Add note about invalid CLI flags when using flat config. (#​17664) (Nicholas C. Zakas)
  • 660ed3a docs: Plugin flat config migration guide (#​17640) (Nicholas C. Zakas)
  • a58aa20 docs: fix examples for several rules (#​17645) (Milos Djermanovic)
  • 179929b docs: Remove trailing newline from the code of Playground links (#​17641) (Francesco Trotta)
  • f8e5c30 docs: Update README (GitHub Actions Bot)
  • b7ef2f3 docs: Enable pretty code formatter output (#​17635) (Nicholas C. Zakas)
  • 0bcb9a8 docs: Fix syntax errors in rule examples (#​17633) (Francesco Trotta)
  • 61b9083 docs: Make no-continue example code work (#​17643) (Zhongyuan Zhou)
  • 9fafe45 docs: upgrade to 11ty 2.0 (#​17632) (Percy Ma)
  • ff8e4bf docs: Update README (GitHub Actions Bot)
  • fab249a docs: Update README (GitHub Actions Bot)
  • 392305b docs: Update no-irregular-whitespace and fix examples (#​17626) (Francesco Trotta)
  • 6b8acfb docs: Add real whitespace to no-trailing-spaces examples (#​17630) (Francesco Trotta)
  • 1000187 docs: Fix examples in unicode-bom (#​17631) (Francesco Trotta)
  • 000290c docs: Update README (GitHub Actions Bot)

Chores

v8.51.0

Compare Source

Features

  • 0a9c433 feat: Add --no-warn-ignored CLI option for flat config (#​17569) (Domantas Petrauskas)
  • 977e67e feat: logical-assignment-operators to report expressions with 3 operands (#​17600) (Yosuke Ota)

Bug Fixes

  • f976b2f fix: make rule severity case-sensitive in flat config (#​17619) (Milos Djermanovic)
  • 0edfe36 fix: Ensure crash error messages are not duplicated (#​17584) (Nicholas C. Zakas)
  • dd79abc fix: eslint-disable to be able to parse quoted rule names (#​17612) (Yosuke Ota)
  • d2f6801 fix: Ensure correct code path for && followed by ?? (#​17618) (Nicholas C. Zakas)

Documentation

  • ee5be81 docs: default to sourceType: "module" in rule examples (#​17615) (Francesco Trotta)
  • 1aa26df docs: Add more examples for multiline-ternary (#​17610) (George Ashiotis)
  • 47d0b44 docs: Update README (GitHub Actions Bot)
  • dbf831e docs: use generated og image (#​17601) (Percy Ma)
  • 1866da5 docs: Update README (GitHub Actions Bot)

Chores

import-js/eslint-plugin-import

v2.29.0

Compare Source

Added
ljharb/tape

v5.7.2

Compare Source

Commits
  • [Refactor] use hasown instead of has 489736a
  • [Deps] update call-bind, mock-property, object-inspect de34703
  • [Tests] use through properly 56d7a8b

v5.7.1

Compare Source

Commits
  • [Fix] default_stream: add handling for IE < 9 13f23ed
  • [Deps] update @ljharb/through, resolve 9135b40
  • Merge tag 'v4.17.0' e61cd40
  • [New] add t.intercept() e60aeca
  • [New] add t.capture and t.captureFn, modeled after tap 3d96d69
  • [Deps] switch from through and resumer to @ljharb/through and @ljharb/resumer a8a7d67
  • [Tests] simplify tests 83bc381
  • [Performance] use inline typeof c45db4e
  • [Deps] update minimist, resolve, string.prototype.trim feee094
  • [Dev Deps] update @ljharb/eslint-config, array.prototype.flatmap, aud 7123111
  • Revert "[meta] ensure not-in-publish‘s absence does not fail anything" 92aaa51
  • [Dev Deps] pin jackspeak since 2.1.2+ depends on npm aliases, which kill the install process in npm < 6 a576f8d

Configuration

📅 Schedule: Branch creation - "on the first day of the month" (UTC), 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

@mend-for-github-com mend-for-github-com bot added the dependencies Pull requests that update a dependency file label Nov 1, 2023
@mend-for-github-com mend-for-github-com bot force-pushed the mend/dev-dependencies branch 2 times, most recently from d544962 to ae8c2ca Compare November 8, 2023 05:06
@mend-for-github-com mend-for-github-com bot force-pushed the mend/dev-dependencies branch 3 times, most recently from 5b952ae to d9a3aed Compare November 21, 2023 05:33
@plegner plegner merged commit 2396d94 into master Nov 27, 2023
6 checks passed
@plegner plegner deleted the mend/dev-dependencies branch November 27, 2023 13:36
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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@plegner