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

44 lines
1.2 KiB
JSON
Raw Normal View History

repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
{
"name": "@angular/platform-server",
chore(package.json): make the packages installable
2016-05-27 19:17:16 -04:00
"version": "0.0.0-PLACEHOLDER",
docs: update descriptions in package.jsons
2016-09-14 19:44:39 -04:00
"description": "Angular - library for using Angular in Node.js",
repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
"author": "angular",
"license": "MIT",
feat(platform-server): update supported range of node versions (#41544) Update the supported range of node versions for Angular. Angular now supports node >=12.14.1 to <16.0.0, dropping support for Node v10. PR Close #41544
2021-04-12 15:13:05 -04:00
"engines": {
fix(platform-server): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822
2021-04-26 14:47:32 -04:00
"node": "^12.14.1 || ^14.0.0"
feat(platform-server): update supported range of node versions (#41544) Update the supported range of node versions for Angular. Angular now supports node >=12.14.1 to <16.0.0, dropping support for Node v10. PR Close #41544
2021-04-12 15:13:05 -04:00
},
repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
"peerDependencies": {
fix(platform-server): setup NoopAnimationsModule in ServerModule by default (#15131) This is so that server side rendering does not throw an exception when it encounters animations on the server side and does not need the user to explicitly setup NoopAnimationsModule in their app server module. Fixes #15098, #14784. PR Close #15131
2017-03-13 20:31:03 -04:00
"@angular/animations": "0.0.0-PLACEHOLDER",
chore(package.json): make the packages installable
2016-05-27 19:17:16 -04:00
"@angular/common": "0.0.0-PLACEHOLDER",
"@angular/compiler": "0.0.0-PLACEHOLDER",
feat(platform-server): bump Domino to v2.0 (#22411) BREAKING CHANGE: * Bump the dependency on Domino to 2.0 to resolve issues with namespacing PR Close #22411
2018-02-23 14:03:22 -05:00
"@angular/core": "0.0.0-PLACEHOLDER",
refactor(compiler): split compiler and core (#18683) After this, neither @angular/compiler nor @angular/comnpiler-cli depend on @angular/core. This add a duplication of some interfaces and enums which is stored in @angular/compiler/src/core.ts BREAKING CHANGE: - `@angular/platform-server` now additionally depends on `@angular/platform-browser-dynamic` as a peer dependency. PR Close #18683
2017-08-16 12:00:03 -04:00
"@angular/platform-browser": "0.0.0-PLACEHOLDER",
refactor: update to tslib 2.0 and move to direct dependencies (#37198) Tslib version is bound to the TypeScript version used to compile the library. Thus, we shouldn't list `tslib` as a `peerDependencies`. This is because, a user can install libraries which have been compiled with older versions of TypeScript and thus require multiple `tslib` versions to be installed. Reference: TOOL-1374 and TOOL-1375 Closes: #37188 PR Close #37198
2020-05-19 08:35:37 -04:00
"@angular/platform-browser-dynamic": "0.0.0-PLACEHOLDER"
fix: platform-server should declare it's dependency on parse5 via package.json
2016-05-03 20:06:04 -04:00
},
"dependencies": {
fix(platform-server): update minimum domino version to latest released (#28893) The version used to test and build from the root package.json is pinned to 2.1.2. This change ensures that users will at a minimum be using the same version. PR Close #28893
2019-02-21 12:07:39 -05:00
"domino": "^2.1.2",
feat(core): support TypeScript 4.2 (#41158) Updates the repo to TypeScript 4.2 and tslib 2.1.0. PR Close #41158
2021-03-16 15:10:32 -04:00
"tslib": "^2.1.0",
fix(platform-server): update `xhr2` dependency (#36366) Previous versions of xhr2 used the depreciated "new Buffer()". Closes #36358 PR Close #36366
2020-04-01 07:35:30 -04:00
"xhr2": "^0.2.0"
adds 'repository' metadata to npm modules (#8649)
2016-05-18 02:17:15 -04:00
},
"repository": {
"type": "git",
build(packaging): add repository.directory field to package.jsons (#27544) PR Close #27544
2018-12-07 06:12:59 -05:00
"url": "https://github.com/angular/angular.git",
"directory": "packages/platform-server"
release: add ng update package group metadata to angular (#22482) "ng update" supports having multiple packages as part of a group which should be updated together, meaning that e.g. calling "ng update @angular/core" would be equivalent to updating all packages of the group (that are part of the package.json already). In order to support the grouping feature, the package.json of the version the user is updating to needs to include an "ng-update" key that points to this metadata. The entire specification for the update workflow can be found here: https://github.com/hansl/devkit/blob/2e8b12a4ef53833dc006e8711acf95cf3a6cf24e/docs/specifications/update.md PR Close #22482
2018-02-27 18:04:35 -05:00
},
"ng-update": {
"packageGroup": "NG_UPDATE_PACKAGE_GROUP"
feat: mark angular packages as side-effect free (#22785) This flag is picked up by webpack v4 and used for more agressive optimizations. Our code is already side-effect free, because that's what we needed for build-optimizer to work. PR Close #22785
2018-03-14 21:30:18 -04:00
},
feat(platform-server): allow shimming the global env sooner (#40559) `@angular/platform-server` provides the foundation for rendering an Angular app on the server. In order to achieve that, it uses a server-side DOM implementation (currently [domino][1]). For rendering on the server to work as closely as possible to running the app on the browser, we need to make DOM globals (such as `Element`, `HTMLElement`, etc.), which are normally provided by the browser, available as globals on the server as well. Currently, `@angular/platform-server` achieves this by extending the `global` object with the DOM implementation provided by `domino`. This assignment happens in the [setDomTypes()][2] function, which is [called in a `PLATFORM_INITIALIZER`][3]. While this works in most cases, there are some scenarios where the DOM globals are needed sooner (i.e. before initializing the platform). See, for example, #24551 and #39950 for more details on such issues. This commit provides a way to solve this problem by exposing a side-effect-ful entry-point (`@angular/platform-server/init`), that shims the `global` object with DOM globals. People will be able to import this entry-point in their server-rendered apps before bootstrapping the app (for example, in their `main.server.ts` file). (See also [#39950 (comment)][4].) In a future update, the [`universal` schematics][5] will include such an import by default in newly generated projects. [1]: https://www.npmjs.com/package/domino [2]: https://github.com/angular/angular/blob/0fc8466f1be392917e0c/packages/platform-server/src/domino_adapter.ts#L17-L21 [3]: https://github.com/angular/angular/blob/0fc8466f1be392917e0c/packages/platform-server/src/server.ts#L33 [4]: https://github.com/angular/angular/issues/39950#issuecomment-747598403 [5]: https://github.com/angular/angular-cli/blob/cc51432661eb4ab4b6a3/packages/schematics/angular/universal PR Close #40559
2021-02-11 12:24:52 -05:00
"sideEffects": [
"./bundles/platform-server-init.umd.js",
"./bundles/platform-server-init.umd.min.js",
"./esm2015/init/src/init.js",
"./fesm2015/init.js",
"./__ivy_ngcc__/bundles/platform-server-init.umd.js",
"./__ivy_ngcc__/esm2015/init/src/init.js",
"./__ivy_ngcc__/fesm2015/init.js"
],
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"
fix(platform-server): require node v8+ (#23331) PR Close #23331
2018-04-12 02:10:28 -04:00
}
repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
}