honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/localize/package.json

43 lines
1011 B
JSON
Raw Normal View History

feat(ivy): implement `$localize()` global function (#31609) PR Close #31609
2019-07-30 13:02:17 -04:00
{
"name": "@angular/localize",
"version": "0.0.0-PLACEHOLDER",
"description": "Angular - library for localizing messages",
feat(ivy): i18n - implement compile-time inlining (#32881) This commit implements a tool that will inline translations and generate a translated copy of a set of application files from a set of translation files. PR Close #32881
2019-10-08 09:46:28 -04:00
"bin": {
feat(localize): implement message extraction tool (#32912) This tool, which can be run from the node_modules bin folder, can parse the source files in your compiled app and generate a translation file formatted with the configured syntax. For example: ``` ./node_modules/.bin/localize-extract -s 'dist/**/*.js' -f xliff1 -o dist/messages.en.xlf ``` PR Close #32912
2019-11-18 05:51:04 -05:00
"localize-translate": "./src/tools/src/translate/main.js",
"localize-extract": "./src/tools/src/extract/main.js"
feat(ivy): i18n - implement compile-time inlining (#32881) This commit implements a tool that will inline translations and generate a translated copy of a set of application files from a set of translation files. PR Close #32881
2019-10-08 09:46:28 -04:00
},
feat(ivy): implement `$localize()` global function (#31609) PR Close #31609
2019-07-30 13:02:17 -04:00
"author": "angular",
"license": "MIT",
"repository": {
"type": "git",
"url": "https://github.com/angular/angular.git"
},
fix(ivy): missing schematics field in localize package (#33025) The schematics added in #32791 is currently failing as the package.json does not reference it. ``` > ng add @angular/localize@9.0.0-next.9 + @angular/localize@9.0.0-next.9 added 1 package from 1 contributor in 6.745s Installed packages for tooling via npm. The package that you are trying to add does not support schematics. You can try using a different version of the package or contact the package author to add ng-add support. ``` PR Close #33025
2019-10-07 06:06:16 -04:00
"schematics": "./schematics/collection.json",
feat(ivy): implement `$localize()` global function (#31609) PR Close #31609
2019-07-30 13:02:17 -04:00
"ng-update": {
"packageGroup": "NG_UPDATE_PACKAGE_GROUP"
},
fix(localize): install `@angular/localize` in `devDependencies` by default (#38680) Previously this package was installed in the default `dependencies` section of `package.json`, but this meant that its own dependencies are treated as dependencies of the main project: Babel, for example. Generally, $localize` is not used at runtime - it is compiled out by the translation tooling, so there is no need for it to be a full dependency. In fact, even if it is used at runtime, the package itself is only used at dev-time since the runtime bits will be bundled into a distributable. So putting this package in `devDependencies` would only prevent libraries from bringing the package into application projects that used them. This is probably good in itself, since it should be up to the downstream project to decide if it wants to include `@angular/localize` at runtime. This commit changes the default location of the package to be the `devDependencies` section, but gives an option `useAtRuntime` to choose otherwise. Fixes #38329 PR Close #38680
2020-09-02 11:16:10 -04:00
"ng-add": {
"save": "devDependencies"
},
feat(ivy): i18n - reorganize entry-points for better reuse (#32488) This is a refactoring that moves the source code around to provide a better platform for adding the compile-time inlining. 1. Move the global side-effect import from the primary entry-point to a secondary entry-point @angular/localize/init. This has two benefits: first it allows the top level entry-point to contain tree-shakable shareable code; second it gives the side-effect import more of an "action" oriented name, which indicates that importing it does something tangible 2. Move all the source code into the top src folder, and import the localize related functions into the localize/init/index.ts entry-point. This allows the different parts of the package to share code without a proliferation of secondary entry-points (i.e. localize/utils). 3. Avoid publicly exporting any utilities at this time - the only public API at this point are the global `$localize` function and the two runtime helpers `loadTranslations()` and `clearTranslations()`. This does not mean that we will not expose additional helpers for 3rd party tooling in the future, but it avoid us preemptively exposing something that we might want to change in the near future. Notes: It is not possible to have the `$localize` code in the same Bazel package as the rest of the code. If we did this, then the bundled `@angular/localize/init` entry-point code contains all of the helper code, even though most of it is not used. Equally it is not possible to have the `$localize` types (i.e. `LocalizeFn` and `TranslateFn`) defined in the `@angular/localize/init` entry-point because these types are needed for the runtime code, which is inside the primary entry-point. Importing them from `@angular/localize/init` would run the side-effect. The solution is to have a Bazel sub-package at `//packages/localize/src/localize` which contains these types and the `$localize` function implementation. The primary `//packages/localize` entry-point imports the types without any side-effect. The secondary `//packages/localize/init` entry-point imports the `$localize` function and attaches it to the global scope as a side-effect, without bringing with it all the other utility functions. BREAKING CHANGES: The entry-points have changed: * To attach the `$localize` function to the global scope import from `@angular/localize/init`. Previously it was `@angular/localize`. * To access the `loadTranslations()` and `clearTranslations()` functions, import from `@angular/localize`. Previously it was `@angular/localize/run_time`. PR Close #32488
2019-08-10 07:51:30 -04:00
"sideEffects": [
"**/init/index.js",
"**/init.js",
"**/localize-init.umd.js"
],
feat(ivy): implement `$localize()` global function (#31609) PR Close #31609
2019-07-30 13:02:17 -04:00
"engines": {
"node": ">=8.0"
feat(ivy): i18n - implement compile-time inlining (#32881) This commit implements a tool that will inline translations and generate a translated copy of a set of application files from a set of translation files. PR Close #32881
2019-10-08 09:46:28 -04:00
},
"dependencies": {
build(localize): sync up babel dependencies (#35008) In #34974 the top level dependency on `@babel/core` was bumped to 7.8.3. This commit ensures that the package.json that gets included in the `@angular/localize` distributable is at the same version. PR Close #35008
2020-01-28 10:02:32 -05:00
"@babel/core": "7.8.3",
feat(ivy): i18n - implement compile-time inlining (#32881) This commit implements a tool that will inline translations and generate a translated copy of a set of application files from a set of translation files. PR Close #32881
2019-10-08 09:46:28 -04:00
"glob": "7.1.2",
build: update to latest "yargs" package (#39749) The 15.x versions of `yargs` relied upon a version of `y18n` that has a SNYK vulnerability. This commit updates the overall project, and therefore also the `localize` and `compiler-cli` packages to use the latest version of `yargs` that does not depend upon the vulnerable `y18n` version. The AIO project was already on the latest `yargs` version and so does not need upgrading. Fixes #39743 PR Close #39749
2020-11-18 14:41:26 -05:00
"yargs": "^16.1.1"
build: set up all packages to publish via wombot proxy (#33747) PR Close #33747
2019-11-11 17:18:13 -05:00
},
refactor(localize): use the `FileSystem` from ngtsc (#36843) This commit makes the leap from its own custom baked `FileUtils` solution to the fully formed `FileSystem` that is used in the compiler-cli. This makes testing more straightforward and helps to ensure that the tool will work across operatings systems. Also, going forward, it will allow the localize project access to other useful code from the compiler-cli, such as source-map handling. PR Close #36843
2020-04-28 16:03:27 -04:00
"peerDependencies": {
"@angular/compiler": "0.0.0-PLACEHOLDER",
"@angular/compiler-cli": "0.0.0-PLACEHOLDER"
Revert "build: remove wombot proxy registry from package.jsons for release (#37378)" (#37495) This reverts commit 26849ca99dcafc45fb8cb0e97af7aeb85ea11852. PR Close #37495
2020-06-08 21:07:39 -04:00
},
"publishConfig": {
"registry": "https://wombat-dressing-room.appspot.com"
feat(ivy): implement `$localize()` global function (#31609) PR Close #31609
2019-07-30 13:02:17 -04:00
}
fix(localize): install `@angular/localize` in `devDependencies` by default (#38680) Previously this package was installed in the default `dependencies` section of `package.json`, but this meant that its own dependencies are treated as dependencies of the main project: Babel, for example. Generally, $localize` is not used at runtime - it is compiled out by the translation tooling, so there is no need for it to be a full dependency. In fact, even if it is used at runtime, the package itself is only used at dev-time since the runtime bits will be bundled into a distributable. So putting this package in `devDependencies` would only prevent libraries from bringing the package into application projects that used them. This is probably good in itself, since it should be up to the downstream project to decide if it wants to include `@angular/localize` at runtime. This commit changes the default location of the package to be the `devDependencies` section, but gives an option `useAtRuntime` to choose otherwise. Fixes #38329 PR Close #38680
2020-09-02 11:16:10 -04:00
}