search

bartblast / hologram

Full stack isomorphic Elixir web framework
Apache License 2.0
349 stars 6 forks source link

Bump the lib-javascript group across 1 directory with 3 updates #108

Closed dependabot[bot] closed 5 months ago

dependabot[bot] commented 5 months ago

Bumps the lib-javascript group with 3 updates in the /assets directory: @biomejs/biome, esbuild and prettier.

Updates @biomejs/biome from 1.7.3 to 1.8.0

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.8.0

Analyzer

New features

  • Allow suppression comments to suppress individual instances of rules. This is used for the lint rule useExhaustiveDependencies, which is now able to suppress specific dependencies. Fixes #2509. Contributed by @​arendjr

Enhancements

  • Assume Astro object is always a global when processing .astro files. Contributed by @​minht11
  • Assume Vue compiler macros are globals when processing .vue files. (#2771) Contributed by @​dyc3

CLI

New features

  • New clean command. Use this new command to clean after the biome-logs directory, and remove all the log files.

    biome clean

  • Add two new options --only and --skip to the command biome lint (#58).

    The --only option allows you to run a given rule or rule group, For example, the following command runs only the style/useNamingConvention and style/noInferrableTypes rules. If the rule is disabled in the configuration, then its severity level is set to error for a recommended rule or warn otherwise.

    biome lint --only=style/useNamingConvention --only=style/noInferrableTypes

    Passing a group does not change the severity level of the rules in the group. All the disabled rules in the group will remain disabled. To ensure that the group is run, the recommended field of the group is enabled. The nursery group cannot be passed, as no rules are enabled by default in the nursery group.

    The --skip option allows you to skip the execution of a given group or a given rule. For example, the following command skips the style group and the suspicious/noExplicitAny rule.

    biome lint --skip=style --skip=suspicious/noExplicitAny

    You can also use --only and --skip together. --skip oevrrides --only. The following command executes only the rules from the style group, but the style/useNamingConvention rule.

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

1.8.0 (2024-06-04)

Analyzer

New features

  • Allow suppression comments to suppress individual instances of rules. This is used for the lint rule useExhaustiveDependencies, which is now able to suppress specific dependencies. Fixes #2509. Contributed by @​arendjr

Enhancements

  • Assume Astro object is always a global when processing .astro files. Contributed by @​minht11
  • Assume Vue compiler macros are globals when processing .vue files. (#2771) Contributed by @​dyc3

CLI

New features

  • New clean command. Use this new command to clean after the biome-logs directory, and remove all the log files.

    biome clean

  • Add two new options --only and --skip to the command biome lint (#58).

    The --only option allows you to run a given rule or rule group, For example, the following command runs only the style/useNamingConvention and style/noInferrableTypes rules. If the rule is disabled in the configuration, then its severity level is set to error for a recommended rule or warn otherwise.

    biome lint --only=style/useNamingConvention --only=style/noInferrableTypes

    Passing a group does not change the severity level of the rules in the group. All the disabled rules in the group will remain disabled. To ensure that the group is run, the recommended field of the group is enabled. The nursery group cannot be passed, as no rules are enabled by default in the nursery group.

    The --skip option allows you to skip the execution of a given group or a given rule. For example, the following command skips the style group and the suspicious/noExplicitAny rule.

    biome lint --skip=style --skip=suspicious/noExplicitAny

    You can also use --only and --skip together. --skip oevrrides --only. The following command executes only the rules from the style group, but the style/useNamingConvention rule.

... (truncated)

Commits
  • 378c05e release: v1.8.0 (#3033)
  • 44b5c29 refactor(noEvolvingAny): rename into noEvolvingTypes (#2959)
  • bc30892 feat(noUnusedFunctionParameters): add lint for unused function parameters, in...
  • 9a7d790 feat: add noLabelWithoutControl rule (#2987)
  • 21e2512 feat: allow "info" severity for analyzer rules (#3014)
  • f793b72 feat(linter): implement useDateNow (#2925)
  • e52084a feat(css_parser): add parsing css modules @​value at rule (#2985)
  • fec262f feat(linter): implement useErrorMessage (#2978)
  • b3da3ae refactor(migrate/eslint): improve naming-convention migration (#2968)
  • 125f34b ci: fix nightly version and restore update of manifest (#2953)
  • Additional commits viewable in compare view


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 prettier from 3.2.5 to 3.3.1

Release notes

Sourced from prettier's releases.

3.3.1

🔗 Changelog

3.3.0

diff

🔗 Release note

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


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