chore(deps): bump loader-utils and @angular-devkit/build-angular
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) andmd4-native(cryptomodule 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) andmd4-native(cryptomodule version) algorithms (cbf9d1d)3.0.0 (2021-10-20)
⚠ BREAKING CHANGES
- minimum supported Node.js version is
12.13.0(93a87ce)- use
xxhash64by default for[hash]/[contenthash]andgetHashDigestAPI[emoji]was removed without replacements, please use custom function if you need this
... (truncated)
Commits
a3fd3cachore(release): 3.2.1d2d752dfix: ReDoS problem (#224)52cd134chore(deps): bump minimist from 1.2.5 to 1.2.6 (#209)9fe2381chore: add .gitattributes for normalizing end of lines - fixes #203 (#204)a282654chore(release): 3.2.0f2a524bchore(deps): update (#200)451858bfeat: hash uniformity for base digestsf7dbfe1chore(release): 3.1.3ef084d4fix: crash with md4 hash (#198)097f5c3chore(release): 3.1.2- Additional commits viewable in compare view
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.xand16.12.x. Current supported versions of Node.js are14.20.x,16.13.xand18.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 unused
appDiroption from Universal and App-Shell schematic. This option can safely be removed if present since it no longer has effect.
analyticsSharingoption 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/coreand@angular-devkit/architect.
@angular-devkit/build-angular
TypeScript versions older than 4.8.2 are no longer supported.
The server builder
bundleDependenciesoption has been removed. This option was used pre Ivy. Currently, using this option is unlikely to produce working server bundles.The
externalDependenciesoption 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
targettoES2022anduseDefineForClassFieldstofalseunless the target is set toES2022or later in the TypeScript configuration. To control ECMA version and features use the Browerslist configuration.
require.contextare 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
bundleDependenciesoption 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
rootis now an error.
@ngtools/webpack
- TypeScript versions older than 4.8.2 are no longer supported.
@schematics/angular
... (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.xand16.12.x. Current minimum versions of Node.js are14.20.0,16.13.0and18.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
appDiroption from Universal and App-Shell schematic. This option can safely be removed if present since it no longer has effect.
analyticsSharingoption 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/coreand@angular-devkit/architect.
@angular-devkit/build-angular
TypeScript versions older than 4.8.2 are no longer supported.
The server builder
bundleDependenciesoption has been removed. This option was used pre Ivy. Currently, using this option is unlikely to produce working server bundles.The
externalDependenciesoption 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
targettoES2022anduseDefineForClassFieldstofalseunless the target is set toES2022or later in the TypeScript configuration. To control ECMA version and features use the Browerslist configuration.
require.contextare 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
bundleDependenciesoption now only accept a boolean value.
... (truncated)
Commits
- See full diff in compare view
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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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 labelswill set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestonewill 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.
@nixel2007 Сможешь решить эту проблему?
Если честно, не совсем понимаю, зачем эта функциональность. При этом это противоречит моему usecase для precommit, поэтому эта штука точно должна быть отключаемой.
Примеры
1 при первом коммите у тебя бинарник имел название Файл1, в каталоге исходников появится каталог с тем же именем Файл1 с нужными исходниками.
На втором коммите ты понимаешь, что название лучше поменять и даешь название Файл2, делаешь коммит, в каталоге исходников появляется каталог Файл2 со всем продублированным содержимым
Но при этом каталог Файл1 не удаляется, т.к. Гит про него ничего не знает
Переименования исходных файлов также может не быть, т.к. у тебя дубль файлов, а не замена названия.
В итоге для одного файла у тебя может быть 2 каталога с продублированным содержимым :(
2 Также может быть вариант, когда бинарник уже удалили из проекта, а каталог исходников остался :(
Например, для проекта xUnitFor1C
- есть несколько похожих наборов src/Tests/CommonApp/ГенерацияМакетаДанных_На_БазеРеальныхДанных и src/Tests/CommonApp/тесты_ГенерацияМакетаДанных_На_БазеРеальныхДанных
- или пример, когда нет бинарника src/Tests/CommonApp/тесты_ОткрытиеФормОтчетовОбработок
- Если переименование делать через git mv, то в диффе гита будет про это написано, эту инфу можно распарсить и соответственно переименовать исходники. Если переименование делали средствами DE/обычным
mv, то в диффе будет строка с удалением и добавлением нового файла. - Эта ситуация тоже будет отражаться в диффе как удаление файла.
Мое предложение - анализировать дифф на предмет именно удаления и переименования обработок. При удалении соответственно удалять старые каталоги. При корректном переименовании через git mv можно так же через git mv переименовывать и папку - так мы еще и историю исходников сохраним.
@nixel2007 Согласен, так лучше Сможешь доработать?
Да, думаю, смогу. Это все будет работать только в режиме git-precommit, правильно понимаю?
Да, конечно