SwiftPackageIndex / SwiftPackageIndex-Server

The Swift Package Index is the place to find Swift packages!
https://swiftpackageindex.com
Apache License 2.0
526 stars 40 forks source link

NPM: Bump the npm-dependencies group with 4 updates #3123

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps the npm-dependencies group with 4 updates: esbuild, esbuild-sass-plugin, prettier and stylelint-scss.

Updates esbuild from 0.21.4 to 0.21.5

Release notes

Sourced from esbuild's releases.

v0.21.5

  • Fix Symbol.metadata on classes without a class decorator (#3781)

    This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

  • Allow unknown import attributes to be used with the copy loader (#3792)

    Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

    // This is an error with "--bundle" without also using "--external:./bagel.js"
    import tasty from "./bagel.js" with { type: "bagel" }
    

    Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

    However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

    // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
    import tasty from "./tasty.bagel" with { type: "bagel" }
    
  • Support import attributes with glob-style imports (#3797)

    This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

    async function loadLocale(locale: string): Locale {
      const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
      return unpackLocale(locale, data)
    }
    

    Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

    ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data
    
    example.ts:2:28:
      2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
        ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~
    

    In addition, this change means plugins can now access the contents of with for glob-style imports.

  • Support ${configDir} in tsconfig.json files (#3782)

    This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.5

  • Fix Symbol.metadata on classes without a class decorator (#3781)

    This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

  • Allow unknown import attributes to be used with the copy loader (#3792)

    Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

    // This is an error with "--bundle" without also using "--external:./bagel.js"
    import tasty from "./bagel.js" with { type: "bagel" }
    

    Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

    However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

    // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
    import tasty from "./tasty.bagel" with { type: "bagel" }
    
  • Support import attributes with glob-style imports (#3797)

    This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

    async function loadLocale(locale: string): Locale {
      const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
      return unpackLocale(locale, data)
    }
    

    Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

    ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data
    
    example.ts:2:28:
      2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
        ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~
    

    In addition, this change means plugins can now access the contents of with for glob-style imports.

  • Support ${configDir} in tsconfig.json files (#3782)

    This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

... (truncated)

Commits


Updates esbuild-sass-plugin from 3.3.0 to 3.3.1

Release notes

Sourced from esbuild-sass-plugin's releases.

v3.3.1

What's Changed

New Contributors

Full Changelog: https://github.com/glromeo/esbuild-sass-plugin/compare/v3.3.0...v3.3.1

Commits
  • f0e58c9 Update package.json
  • 0151ef4 Merge pull request #179 from dungjk/feature/named_exports
  • 6dba8bd style: update coding style to align with source code conventions
  • 6abbf37 feat: Add support namedExports
  • e6519ee Update package.json
  • See full diff in compare view


Updates prettier from 3.3.0 to 3.3.1

Release notes

Sourced from prettier's releases.

3.3.1

🔗 Changelog

Changelog

Sourced from prettier's changelog.

3.3.1

diff

Preserve empty lines in front matter (#16347 by @​fisker)

<!-- Input -->
---
foo:
  - bar1
  • bar2

  • bar3


Markdown

<!-- Prettier 3.3.0 -->


foo:

  • bar1
  • bar2
  • bar3

Markdown

<!-- Prettier 3.3.1 -->

foo:

  • bar1

  • bar2

  • bar3


Markdown

Preserve explicit language in front matter (#16348 by @​fisker)

<!-- Input -->
---yaml
</tr></table> 

... (truncated)

Commits


Updates stylelint-scss from 6.3.0 to 6.3.1

Release notes

Sourced from stylelint-scss's releases.

6.3.1

  • Fixed: selector-no-redundant-nesting-selector handle pseudo selectors (#1008).
  • Fixed: operator-no-unspaced handle Tailwind CSS direct children styling (#1007).
  • Fixed: no-unused-private-members fix changes from hyphen to underscore in debug message (#1002).

Full Changelog: https://github.com/stylelint-scss/stylelint-scss/compare/v6.3.0...v6.3.1

Changelog

Sourced from stylelint-scss's changelog.

6.3.1

  • Fixed: selector-no-redundant-nesting-selector handle pseudo selectors (#1008).
  • Fixed: operator-no-unspaced handle Tailwind CSS direct children styling (#1007).
  • Fixed: no-unused-private-members fix changes from hyphen to underscore in debug message (#1002).

Full Changelog: https://github.com/stylelint-scss/stylelint-scss/compare/v6.3.0...v6.3.1

Commits
  • 9cd9e62 6.3.1
  • f0415e0 Prepare version 6.3.1
  • 82aa0e9 selector-no-redundant-nesting-selector: handle pseudo selectors (#1008)
  • 80502d7 operator-no-unspaced: handle Tailwind CSS direct children styling (#1007)
  • 192441f Fix changes from hyphen to underscore in debug message (#1002)
  • a4004cc build(deps-dev): bump stylelint from 16.5.0 to 16.6.1 (#1006)
  • 3d6d2e0 build(deps): bump postcss-selector-parser from 6.0.16 to 6.1.0 (#1005)
  • 14756be build(deps): bump known-css-properties from 0.30.0 to 0.31.0 (#1004)
  • See full diff in compare view


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions