demos icon indicating copy to clipboard operation
demos copied to clipboard

chore(deps): bump loader-utils and @angular-devkit/build-angular

Open dependabot[bot] opened this issue 3 years ago • 0 comments

Bumps loader-utils to 3.2.1 and updates ancestor dependency @angular-devkit/build-angular. These dependencies need to be updated together.

Updates loader-utils from 1.2.3 to 3.2.1

Release notes

Sourced from loader-utils's releases.

v3.2.1

3.2.1 (2022-11-11)

Bug Fixes

v3.2.0

3.2.0 (2021-11-11)

Features

  • hash uniformity for base digests (451858b)

v3.1.3

3.1.3 (2021-11-04)

Bug Fixes

v3.1.2

3.1.2 (2021-11-04)

Bug Fixes

v3.1.1

3.1.1 (2021-11-04)

Bug Fixes

  • base64 and unicode characters (02b1f3f)

v3.1.0

3.1.0 (2021-10-29)

Features

  • added md4 (wasm version) and md4-native (crypto module version) algorithms (cbf9d1d)

v3.0.0

3.0.0 (2021-10-20)

... (truncated)

Changelog

Sourced from loader-utils's changelog.

3.2.1 (2022-11-11)

Bug Fixes

3.2.0 (2021-11-11)

Features

  • hash uniformity for base digests (451858b)

3.1.3 (2021-11-04)

Bug Fixes

3.1.2 (2021-11-04)

Bug Fixes

3.1.1 (2021-11-04)

Bug Fixes

  • base64 and unicode characters (02b1f3f)

3.1.0 (2021-10-29)

Features

  • added md4 (wasm version) and md4-native (crypto module version) algorithms (cbf9d1d)

3.0.0 (2021-10-20)

⚠ BREAKING CHANGES

  • minimum supported Node.js version is 12.13.0 (93a87ce)
  • use xxhash64 by default for [hash]/[contenthash] and getHashDigest API
  • [emoji] was removed without replacements, please use custom function if you need this

... (truncated)

Commits

Updates @angular-devkit/build-angular from 0.801.3 to 15.0.0

Release notes

Sourced from @​angular-devkit/build-angular's releases.

v15.0.0

15.0.0 (2022-11-16)

Breaking Changes

@​angular/cli

  • The Angular CLI no longer supports 16.10.x, 16.11.x and 16.12.x. Current supported versions of Node.js are 14.20.x, 16.13.x and 18.10.x.
  • Node.js versions older than 14.20 are no longer supported.
  • The 'path' option in schematics schema no longer has a special meaning. Use 'workingDirectory' smart default provider should be used instead.

@​schematics/angular

  • Removed unusedappDir option from Universal and App-Shell schematic. This option can safely be removed if present since it no longer has effect.

  • analyticsSharing option in the global angular configuration has been removed without replacement. This option was used to configure the Angular CLI to access to your own users' CLI usage data.

    If this option is used, it can be removed using ng config --global cli.analyticsSharing undefined.

  • analytics APIs have been removed without replacement from @angular-devkit/core and @angular-devkit/architect.

@​angular-devkit/build-angular

  • TypeScript versions older than 4.8.2 are no longer supported.

  • The server builder bundleDependencies option has been removed. This option was used pre Ivy. Currently, using this option is unlikely to produce working server bundles.

    The externalDependencies option can be used instead to exclude specific node_module packages from the final bundle.

    • Deprecated support for tilde import has been removed. Please update the imports by removing the ~.

    Before

    @import "~font-awesome/scss/font-awesome";
    

    After

    @import "font-awesome/scss/font-awesome";
    
    • By default the CLI will use Sass modern API, While not recommended, users can still opt to use legacy API by setting NG_BUILD_LEGACY_SASS=1.
  • Internally the Angular CLI now always set the TypeScript target to ES2022 and useDefineForClassFields to false unless the target is set to ES2022 or later in the TypeScript configuration. To control ECMA version and features use the Browerslist configuration.

  • require.context are no longer parsed. Webpack specific features are not supported nor guaranteed to work in the future.

  • Producing ES5 output is no longer possible. This was needed for Internet Explorer which is no longer supported. All browsers that Angular supports work with ES2015+

  • server builder bundleDependencies option now only accept a boolean value.

  • Deprecated support for Stylus has been removed. The Stylus package has never reached a stable version and its usage in the Angular CLI is minimal. It's recommended to migrate to another CSS preprocessor that the Angular CLI supports.

@​angular-devkit/core

  • Workspace projects with missing root is now an error.

@​ngtools/webpack

  • TypeScript versions older than 4.8.2 are no longer supported.

@​schematics/angular

Commit Description
feat - 766d4a089 add migration to remove require calls from karma builder main file
feat - d8bff4f1e Added --project-root option to the library schematics
feat - 597bfea1b drop polyfills.ts file from new templates
feat - 1c21e470c enable error on unknown properties and elements in tests

... (truncated)

Changelog

Sourced from @​angular-devkit/build-angular's changelog.

15.0.0 (2022-11-16)

Breaking Changes

@​angular/cli

  • The Angular CLI no longer supports 16.10.x, 16.11.x and 16.12.x. Current minimum versions of Node.js are 14.20.0, 16.13.0 and 18.10.0.
  • Node.js versions older than 14.20 are no longer supported.
  • The 'path' option in schematics schema no longer has a special meaning. Use 'workingDirectory' smart default provider should be used instead.

@​schematics/angular

  • Removed unused appDir option from Universal and App-Shell schematic. This option can safely be removed if present since it no longer has effect.

  • analyticsSharing option in the global angular configuration has been removed without replacement. This option was used to configure the Angular CLI to access to your own users' CLI usage data.

    If this option is used, it can be removed using ng config --global cli.analyticsSharing undefined.

  • analytics APIs have been removed without replacement from @angular-devkit/core and @angular-devkit/architect.

@​angular-devkit/build-angular

  • TypeScript versions older than 4.8.2 are no longer supported.

  • The server builder bundleDependencies option has been removed. This option was used pre Ivy. Currently, using this option is unlikely to produce working server bundles.

    The externalDependencies option can be used instead to exclude specific node_module packages from the final bundle.

    • Deprecated support for tilde import has been removed. Please update the imports by removing the ~.

    Before

    @import '~font-awesome/scss/font-awesome';
    

    After

    @import 'font-awesome/scss/font-awesome';
    
    • By default the CLI will use Sass modern API, While not recommended, users can still opt to use legacy API by setting NG_BUILD_LEGACY_SASS=1.
  • Internally the Angular CLI now always set the TypeScript target to ES2022 and useDefineForClassFields to false unless the target is set to ES2022 or later in the TypeScript configuration. To control ECMA version and features use the Browerslist configuration.

  • require.context are no longer parsed. Webpack specific features are not supported nor guaranteed to work in the future.

  • Producing ES5 output is no longer possible. This was needed for Internet Explorer which is no longer supported. All browsers that Angular supports work with ES2015+

  • server builder bundleDependencies option now only accept a boolean value.

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by google-wombot, a new releaser for @​angular-devkit/build-angular since your current version.


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 ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependabot[bot] avatar Nov 19 '22 08:11 dependabot[bot]

@nixel2007 Сможешь решить эту проблему?

artbear avatar Nov 27 '15 12:11 artbear

Если честно, не совсем понимаю, зачем эта функциональность. При этом это противоречит моему usecase для precommit, поэтому эта штука точно должна быть отключаемой.

nixel2007 avatar Nov 27 '15 12:11 nixel2007

Примеры 1 при первом коммите у тебя бинарник имел название Файл1, в каталоге исходников появится каталог с тем же именем Файл1 с нужными исходниками. На втором коммите ты понимаешь, что название лучше поменять и даешь название Файл2, делаешь коммит, в каталоге исходников появляется каталог Файл2 со всем продублированным содержимым Но при этом каталог Файл1 не удаляется, т.к. Гит про него ничего не знает Переименования исходных файлов также может не быть, т.к. у тебя дубль файлов, а не замена названия.

В итоге для одного файла у тебя может быть 2 каталога с продублированным содержимым :(

2 Также может быть вариант, когда бинарник уже удалили из проекта, а каталог исходников остался :(

Например, для проекта xUnitFor1C

artbear avatar Nov 27 '15 14:11 artbear

  1. Если переименование делать через git mv, то в диффе гита будет про это написано, эту инфу можно распарсить и соответственно переименовать исходники. Если переименование делали средствами DE/обычным mv, то в диффе будет строка с удалением и добавлением нового файла.
  2. Эта ситуация тоже будет отражаться в диффе как удаление файла.

Мое предложение - анализировать дифф на предмет именно удаления и переименования обработок. При удалении соответственно удалять старые каталоги. При корректном переименовании через git mv можно так же через git mv переименовывать и папку - так мы еще и историю исходников сохраним.

nixel2007 avatar Nov 27 '15 14:11 nixel2007

@nixel2007 Согласен, так лучше Сможешь доработать?

artbear avatar Nov 27 '15 14:11 artbear

Да, думаю, смогу. Это все будет работать только в режиме git-precommit, правильно понимаю?

nixel2007 avatar Nov 27 '15 15:11 nixel2007

Да, конечно

artbear avatar Nov 27 '15 15:11 artbear