chrisguttandin / angular-prerender Goto Github PK

View Code? Open in Web Editor NEW

125.0 7.0 7.0 11.63 MB

A command line tool to prerender Angular Apps.

License: MIT License

JavaScript 54.94% TypeScript 44.75% Shell 0.31%

angular cli command-line ngx server-side-rendering static-site-generator

angular-prerender's People

Stargazers

Watchers

Forkers

joejordanbrown samvloeberghs cristian-guerrero villeharjunen bathrimohan bittlerr indigofaol

angular-prerender's Issues

An in-range update of eslint-config-holy-grail is breaking the build 🚨

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency eslint-config-holy-grail was updated from `46.0.14` to `46.0.15`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-holy-grail is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ Travis CI - Branch: The build failed.

Release Notes for v46.0.15

all commits

Commits

The new version differs by 5 commits.

ccb7f59 46.0.15
2ef727f fix(package): update eslint-plugin-unicorn to version 19.0.0
0faf580 fix(package): update lockfile
758c948 fix(package): update husky to version 4.2.5
9f66f3c fix(package): update commitizen to version 4.0.4

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of husky is breaking the build 🚨

The devDependency husky was updated from `3.0.1` to `3.0.2`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

husky is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ Travis CI - Branch: The build failed.

Release Notes for v3.0.2

Fix: add shebang to run.js (#528)

Commits

The new version differs by 5 commits.

bf2659b 3.0.2
e216752 Update FUNDING.yml
f955c07 extract getGitHooks function in installer/index.ts (#551)
b7c2705 Add shebang to run.js (#528)
5bcf721 Update CHANGELOG.md

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Atob is not defined

When using angular-prerender with angular 9 application, it crashes on

.../node_modules/zone.js/dist/zone-node.js:192
throw error;

ReferenceError: atob is not defined

An in-range update of husky is breaking the build 🚨

The devDependency husky was updated from `4.0.8` to `4.0.9`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ Travis CI - Branch: The build failed.

Release Notes for v4.0.9

Fix: read stdin from hook script (#645)

Commits

The new version differs by 2 commits ahead by 2, behind by 2.

93b3fc6 4.0.9
0eb20f2 read stdin from hook script (#645)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of tslint-config-holy-grail is breaking the build 🚨

The devDependency tslint-config-holy-grail was updated from `44.0.6` to `44.0.7`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tslint-config-holy-grail is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 12 commits.

5535eb9 44.0.7
45007ed fix(package): update zone.js to version 0.10.0
c1b665e fix(package): update mocha to version 6.2.0
3741d26 fix(package): update load-grunt-config to version 2.0.1
8a37c0f fix(package): update husky to version 3.0.1
20ddae7 fix(package): update eslint-config-holy-grail to version 38.0.3
bfe90cf fix(package): update eslint to version 6.1.0
6c5c539 fix(package): update cz-conventional-changelog to version 3.0.2
74bf378 fix(package): update commitizen to version 4.0.3
7218445 fix(package): update @angular/{compiler,core} to version 8.1.3
3e11a52 fix(package): update @commitlint/config-angular to version 8.1.0
3b9c5b2 fix(package): update @commitlint/cli to version 8.1.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Please install ts-evaluator instead

An in-range update of @angular-devkit/core is breaking the build 🚨

The dependency @angular-devkit/core was updated from `7.2.1` to `7.2.2`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular-devkit/core is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build failed.

Release Notes for v7.2.2

Commits

@schematics/angular (7.2.2)
Commit	Description	Notes
	assert no error logs in e2e
	fix syntax error in main.ts after generating universal	[Closes #13392]
	remove properties which are set by default from required	[Closes #13010]
@angular-devkit/build-angular (0.12.2)
Commit	Description	Notes
	script chunk in angular.json return false then calling isInitial
	`vendorSourceMap` not being recognized when passed directly	[Closes #13414]
	only show production warning when having either styles on scripts optimization turn on	[Closes #13415]
	add missing declaration types in build_angular schemas.	[Closes #13388]
	prints a warning on --host on serve	[Closes #11060]
@angular-devkit/build-optimizer (0.12.2)
Commit	Description	Notes
	support windows paths in rollup plugin
@angular-devkit/core (7.2.2)
Commit	Description	Notes
	Make default and info log messages use default colors	[Closes #13439]
@ngtools/webpack (7.2.2)
Commit	Description	Notes
	drop only unused default import when used with named imports
@schematics/update (0.12.2)
Commit	Description	Notes
	ensure option is string when replacing environment variable references

Special Thanks

Alan, Alan Agius, Keen Yee Liau, Renovate Bot, Johannes Steier, Mikel Ward, Matthias Gaudin, Hans Larsen, Filipe Silva, Moritz Benzenhöfer, 調月奏

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of tslint-config-holy-grail is breaking the build 🚨

The devDependency tslint-config-holy-grail was updated from `37.0.0` to `37.0.1`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 4 commits.

80d7901 37.0.1
0e6a240 fix(package): update @angular/{compiler,core} to version 7.0.4
9d48687 fix(package): update husky to version 1.1.4
4f3f5a3 fix(package): update eslint to version 5.9.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Improve parameter-values

Since Angular prerendering in general and angular-prerenderer specifially finally works for me, I now tried to care about the details. With no luck so far. It is great that angular-prerenderer offers the param parameter-values, but its usage is either not well documented or it doesn't work for my scenario.

Consider these route definitions

const routes: Routes = [
    {
        path: "/bar",
        component: HomeComponent
    },
    {
        path: "/route-i-want-to-prerender/:id/:title",
        component: WhatEver
    },
    {
        path: "/route-i-do-not-want-to-prerender/:id/:title",
        component: AnotherOne,
    }
]

First problem: Params have the same name across routes, but there is just one route for which I want to pass params (or I want to pass different params per route).
Second problem: There are multiple params per route. If I pass the params like
'{":id":["1","2","3"],":title":["foo1","foo2","foo3"]
I expect the routes below to be prerendered

/route-i-want-to-prerender/1/foo1
/route-i-want-to-prerender/2/foo2
/route-i-want-to-prerender/3/foo3

However, instead of 3 routes, angular-prerenderer produced 9. I don't get exactly what happens here, but it is wrong for my use case.

Finally, I'd prefer to be able to pass a JSON file (or a path pointing to a JSON file, to be more precise) instead of a string. That way, you get rid of escaping problems and you won't run into any length restriction issues on the command line.

In my opinion, the expected structure of that JSON file should be something like this

{
    "/route-i-want-to-prerender/:id/:title": [
        { ":id": "1", ":title": "foo1" },
        { ":id": "2", ":title": "foo2" },
        { ":id": "3", ":title": "foo3" }
    ],
    "/another-route-i-want-to-prerender/:id/:title": [
        { ":id": "4", ":title": "bar4" },
        { ":id": "5", ":title": "bar5" },
        { ":id": "6", ":title": "bar6" }
    ],
}

Issue with i18n

Hi @chrisguttandin, Thank you again for your great contributions.
Sorry to bother you again, I found an issue when you build the project with multi locale (i18n).
You can check this demo project also to reproduce the issue (I pushed the last changes that you fixed in #87):

https://github.com/keserwan/testAngularPrerender

To reporduce it, you run the following commands:

npm i
npm run build:i18n-ssr
npx angular-prerender

npm run build:i18n-ssr: this command will create 2 folders "ar" and "en" in "dist/website/server" and "dist/website/browser".

I am getting this error after calling "npx angular-prerender"
Knowing that main.js is not available in "dist/website/server", it is available in the two folders "en" and "ar".

(node:26332) UnhandledPromiseRejectionWarning: Error: Cannot find module 'C:\Development\test\testPrerender\dist\website\server\main'
Require stack:
- C:\Development\test\testPrerender\node_modules\angular-prerender\build\node\functions\prerender.js
- C:\Development\test\testPrerender\node_modules\angular-prerender\build\node\app.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:623:15)
    at Function.Module._load (internal/modules/cjs/loader.js:527:27)
    at Module.require (internal/modules/cjs/loader.js:681:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at prerender (C:\Development\test\testPrerender\node_modules\angular-prerender\build\node\functions\prerender.js:74:7)
    at C:\Development\test\testPrerender\node_modules\angular-prerender\build\node\app.js:78:3
(node:26332) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:26332) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
PS C:\Development\test\testPrerender>

An in-range update of @angular-devkit/core is breaking the build 🚨

The dependency @angular-devkit/core was updated from `8.1.2` to `8.1.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular-devkit/core is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build failed.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @angular-devkit/core is breaking the build 🚨

The dependency @angular-devkit/core was updated from `8.2.2` to `8.3.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular-devkit/core is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build failed.

Release Notes for v8.3.0

Commits

@schematics/angular (8.3.0)
Commit	Description	Notes
	add twitter link icon (#15385)
	default interface for guard

Special Thanks

Judy Bogart, Keen Yee Liau, Stefanie Fluin, Charles Lyding, Alan Agius, Cédric Exbrayat

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

npx error

Hi there, just wanted to let you know that it works nicely for the simple testing app I got. However, it seems right now you have to add angular-prerender to the dependencies, npx angular-prerender throws an error (even with the simple universal example from the readme).

→ npx angular-prerender
No routes could be retrieved thus the default route at "/" will be added.
(node:33634) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'subscribe' of undefined
    at new ApplicationRef (/Users/rweng/Code/playground/universe/node_modules/@angular/core/bundles/core.umd.js:16824:41)
    at _createClass (/Users/rweng/Code/playground/universe/node_modules/@angular/core/bundles/core.umd.js:19860:24)
    at _createProviderInstance (/Users/rweng/Code/playground/universe/node_modules/@angular/core/bundles/core.umd.js:19822:30)
    at initNgModule (/Users/rweng/Code/playground/universe/node_modules/@angular/core/bundles/core.umd.js:19755:36)
    at new NgModuleRef_ (/Users/rweng/Code/playground/universe/node_modules/@angular/core/bundles/core.umd.js:20482:13)
    at createNgModuleRef (/Users/rweng/Code/playground/universe/node_modules/@angular/core/bundles/core.umd.js:20471:16)
    at Object.debugCreateNgModuleRef [as createNgModuleRef] (/Users/rweng/Code/playground/universe/node_modules/@angular/core/bundles/core.umd.js:22302:16)
    at NgModuleFactory_.create (/Users/rweng/Code/playground/universe/node_modules/@angular/core/bundles/core.umd.js:23030:29)
    at /Users/rweng/.npm/_npx/33634/lib/node_modules/angular-prerender/node_modules/@angular/core/bundles/core.umd.js:16667:47
    at ZoneDelegate.invoke (/Users/rweng/.npm/_npx/33634/lib/node_modules/angular-prerender/node_modules/zone.js/dist/zone-node.js:388:26)
(node:33634) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:33634) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

An in-range update of commitizen is breaking the build 🚨

The devDependency commitizen was updated from `3.0.2` to `3.0.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

commitizen is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ Travis CI - Branch: The build failed.

Release Notes for v3.0.3

3.0.3 (2018-10-19)

Bug Fixes

config loader: deal with config file charset (#525) (c74eeb9e)

Commits

The new version differs by 4 commits.

c74eeb9 fix(config loader): deal with config file charset (#525)
42c8bb6 docs: fix link to external adapter (#581)
9e05c28 docs: add esg github adapter to the docs (#579)
2965fe6 docs: add another JIRA adapter (#576)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

angular-prerender creates huge HTML file with CSS and source map

In my Angular 8 project, when running ng build --prod
everything seems to work fine. I have sourceMap set to false in angular.json, and indeed no source map files are created. My styles... .css file is just 170kb large

However, after running npx angular-prerender, the result seems somewhat weird. My index.html is now 6,4mb large.
The content consists mainly of CSS.
While the <body> of this HTML page is quite small (18kb), the header is huge.
Namely, there are eight <style> tags all starting like <style ng-transition="serverApp">
Every <style> tag has a source map comment in base64 format starting like /*# sourceMappingURL=data:application/json;base64...
All these comments are in sum ca 5MB large.

The rest of the <head> is plain CSS (which somehow seem repetitive), so ca. 1.8MB

My questions are now:

Where do these source map comments come from? Why they are there when sourceMaps are turned off in angular.json?
Why is the CSS so huge anyway when the .css file created by ng build is actually very small?

An in-range update of tsconfig-holy-grail is breaking the build 🚨

The devDependency tsconfig-holy-grail was updated from `6.0.8` to `6.0.9`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tsconfig-holy-grail is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 6 commits.

62069a9 6.0.9
cd0292e fix(package): update @types/node to version 10.11.1
414532e fix(package): update husky to version 1.0.1
745a24f fix(package): update husky to version 1.0.0
0985f98 fix(package): update chai to version 4.2.0
31b3509 fix(package): update lockfile

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @types/yargs is breaking the build 🚨

The devDependency @types/yargs was updated from `13.0.0` to `13.0.1`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/yargs is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ Travis CI - Branch: The build failed.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of commitlint is breaking the build 🚨

There have been updates to the commitlint monorepo:

- The devDependency @commitlint/cli was updated from 8.0.0 to 8.1.0.

The devDependency @commitlint/config-angular was updated from 8.0.0 to 8.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the commitlint group definition.

commitlint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ Travis CI - Branch: The build errored.

Commits

The new version differs by 39 commits.

c17420d v8.1.0
ca19d70 chore: update dependency lodash to v4.17.14 (#724)
5757ef2 build(deps): bump lodash.template from 4.4.0 to 4.5.0 (#721)
5b5f855 build(deps): bump lodash.merge from 4.6.0 to 4.6.2 (#722)
4cb979d build(deps): bump lodash from 4.17.11 to 4.17.13 (#723)
a89c1ba chore: add devcontainer setup
9aa5709 chore: pin dependencies (#714)
c9ef5e2 chore: centralize typescript and jest setups (#710)
c9dcf1a chore: pin dependencies (#708)
6a6a8b0 refactor: rewrite top level to typescript (#679)
0fedbc0 chore: update dependency @types/jest to v24.0.15 (#694)
0b9c7ed chore: update dependency typescript to v3.5.2 (#695)
4efb34b chore: update dependency globby to v10 (#705)
804af8b chore: update dependency lint-staged to v8.2.1 (#696)
9075844 fix: add explicit dependency on chalk (#687)

There are 39 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Error: Multiple root routing modules found

I'm still getting an error while adding lazy loaded routes to my Angular project. According to #87 and #82 the error should be fixed, but it isn't.

Error:

UnhandledPromiseRejectionWarning: Error: Multiple root routing modules found C:\Users\Toni\Source\test\universe\src\app\lazy\lazy-routing.module.ts, C:\Users\Toni\Source\test\universe\src\app\app-routing.module.ts
    at findRootModule (C:\Users\Toni\Source\test\universe\node_modules\guess-parser\dist\guess-parser\index.js:419:15)
    at exports.parseRoutes (C:\Users\Toni\Source\test\universe\node_modules\guess-parser\dist\guess-parser\index.js:582:31)
    at prerender (C:\Users\Toni\Source\test\universe\node_modules\angular-prerender\build\node\functions\prerender.js:89:54)

I'm using the following commands to create the project:

ng new universe --routing
cd universe
ng generate universal --client-project universe
ng generate module lazy --route lazy --module app
ng build
ng run universe:server
npx angular-prerender

My environment is:

Angular CLI: 8.3.14
Node: 12.12.0
OS: win32 x64
Angular: 8.2.12

And the version of angular-prerender that is being used is 4.1.21.

Is there a workaround or different syntax for adding lazy loaded routes/modules to the project? Are lazy loaded routes actually supported?

An in-range update of tsconfig-holy-grail is breaking the build 🚨

The devDependency tsconfig-holy-grail was updated from `10.0.26` to `10.0.27`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ Travis CI - Branch: The build errored.

Commits

The new version differs by 3 commits.

09e06ad 10.0.27
6307917 fix(package): update typescript to version 3.7.2
fb97658 fix(package): update @types/node to version 12.12.6

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @angular-devkit/core is breaking the build 🚨

The dependency @angular-devkit/core was updated from `8.3.24` to `8.3.25`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular-devkit/core is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build errored.

Release Notes for v8.3.25

Commits

Misc
Commit	Description	Notes
	remove alias for ng doc command
@angular-devkit/build-angular (0.803.25)
Commit	Description	Notes
	provide supported browsers to babel
	add crossorigin attribute to lazy chunks	[Closes #16801]

Special Thanks

Alan Agius, Charles Lyding, Minko Gechev

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Support request: possible to deploy as cloud function?

I am looking to deploy a cloud function that can prerender a few urls. I am looking into different ways, but very new to Universal and ssr. Would it be possible to use this library as a cloud function?
Thanks,

An in-range update of tslint-config-holy-grail is breaking the build 🚨

The devDependency tslint-config-holy-grail was updated from `36.0.3` to `36.0.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 8 commits.

9b5fd5f 36.0.4
009220a fix(package): update commitizen to version 3.0.3
e8c4b58 fix(package): update @angular/{common,compiler,core} to version 7.0.0
0254eae fix(package): update eslint to version 5.7.0
f046fdc fix(package): update typescript to version 3.1.3
cd3bf5d fix(package): update @commitlint/cli to version 7.2.1
1309d4f fix(package): update husky to version 1.1.2
d91d760 fix(package): update lockfile

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Feature Request: option for prerendering routes from a txt file --include-routes-file

Hi @chrisguttandin,

Can I request functionality to accept a command line argument eg --include-routes-file, that accepts relative path to a txt file.
The txt file will contain routes for all pages that should be prerendered by angular-prerender.

Thanks in advance

How to use this plugin with https://prerender.io/

We have developed an app in angular and now planning to use https://prerender.io/ in our app. So, is it possible to use this plugin (angular-prerender) with https://prerender.io/. If yes then how can we pass prerender.io token to this plugin. Please add some code snippet for this implementation with prerender.io token and angular-prerender plugin.

Thanks,
Ajay

An in-range update of @angular-devkit/core is breaking the build 🚨

Version 0.7.5 of @angular-devkit/core was just published.

Branch	Build failing 🚨
Dependency	@angular-devkit/core
Current Version	0.7.4
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

@angular-devkit/core is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
❌ Travis CI - Branch: The build failed.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Not picking up the routes array in angular.json

Had to install it with --force in Angular 15, probably not related but angular-prerender is not picking up the routes in angular.json.

I can use the --include-routes but it gets fairly impractical with many routes.
To simplify the task, I've added the command to the scripts in package.json, but I wouldn't like to add all the routes there.

There's probably a better way to do it but I'm not too familiar with node scripts & it would seem redundant since angular.json already gives the option

All those routes are dynamic routes with parameters, I wasn't able to use the --parameter-values flag, getting a number of errors related to the format of the json string

Basic project example seems to be missing a step

Hi,

I've been playing with this package a bit, it's really cool

It'll be obvious for people who are used to modern builds, but the basic project example seems to omit the "npm install" step, which is necessary to do before the "ng build" step.

Thanks for the new toy to play with, cheers

An in-range update of guess-parser is breaking the build 🚨

The dependency guess-parser was updated from `0.4.12` to `0.4.13`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

guess-parser is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 35 commits.

dc84c12 v0.4.13
e754835 Update package-lock.json
1125a95 Update dependency googleapis to v47 (#303)
3f1b7fe Update dependency @types/jest to v24.9.0 (#302)
f901574 Handle path mappings in Nx monorepos (#300)
164ed04 Update dependency ts-node to v8.6.2 (#301)
6512c1e Update dependency ts-node to v8.6.1 (#299)
9282ed5 Update dependency ts-node to v8.6.0 (#298)
83acbe3 Update dependency http-server to v0.12.1 (#297)
98699d4 Update dependency ts-jest to v24.3.0 (#296)
af3ee44 Update dependency mocha to v7 (#295)
787bba7 Update dependency lerna to v3.20.2 (#294)
59b247c Update dependency lerna to v3.20.1 (#293)
2692ae0 Update dependency webpack to v4.41.5 (#292)
2b72cda Update dependency lerna to v3.20.0 (#291)

There are 35 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Argument `--parameter-values` gives JSON parse error

Running with the option --parameter-values as documented does not work, but gives a JSON parse exception:

PS C:\my-dir> npx angular-prerender --parameter-values '{":name":["amelia","oliver"]}'
Opties:
  --version           Toon versienummer                              [booleaans]
  --help              Toon help                                      [booleaans]
  --browser-target    specify the target inside your angular.json file which is
                      used to build the single page app
                                                   [string] [standaard: "build"]
  --config            specify the path to the angular.json file
                                                            [string] [standaard:
               "C:\mydir\angular.json"]
  --parameter-values  specify the parameter values which should be replaced with
                      the parameter in the routes     [string] [standaard: "{}"]
  --server-target     specify the target inside your angular.json file which is
                      used to build the server side code
                                                  [string] [standaard: "server"]
  --verbose, -v       set this flag if you prefer more detailed log messages
                                                  [booleaans] [standaard: false]

Unexpected token : in JSON at position 1

I tried other ways but did not yet succeed, except with an empty map: PS C:\my-dir> npx angular-prerender --parameter-values '{}'

An in-range update of @angular-devkit/core is breaking the build 🚨

The dependency @angular-devkit/core was updated from `7.2.3` to `7.2.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular-devkit/core is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build failed.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

MODULE_MAP instance loaded by angular-prerender is not the same as the one used by the server module

First of all, thank you so much for creating this repo!

When I bumped angular-prerender from 4.1.5 to latest, I ran into this error:
NullInjectorError: No provider for InjectionToken MODULE_MAP!

After digging in a little bit, I think it's related to the deferred loading of the @nguniversal/module-map-ngfactory-loader (in particular, https://github.com/chrisguttandin/angular-prerender/blob/master/src/functions/load-peer-dependencies.ts#L39).

I believe how it's being executed there, the MODULE_MAP from @nguniversal/module-map-ngfactory-loader (https://github.com/angular/universal/blob/991472d1abe721d2ebba8c5faf89f7177a95bc68/modules/module-map-ngfactory-loader/src/module-map-ngfactory-loader.ts#L22) is being recreated. The one that is used in ModuleMapLoaderModule is the existing MODULE_MAP and DI isn't matching the two together.

An in-range update of @angular-devkit/core is breaking the build 🚨

The dependency @angular-devkit/core was updated from `7.0.5` to `7.0.6`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular-devkit/core is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build failed.

Release Notes for v7.0.6

Commits

@angular/cli (7.0.6)
Commit	Description	Notes
	add missing `ngswConfigPath` to schema
@schematics/angular (7.0.6)
Commit	Description	Notes
	`addSymbolToNgModuleMetadata` metadata without indent	[Closes #12950]
	rename e2e PO utility function
@angular-devkit/core (7.0.6)
Commit	Description	Notes
	handle drive only paths in windows	[Closes #12670]
@ngtools/webpack (7.0.6)
Commit	Description	Notes
	update error message to reference templateUrl	[Closes #12693]

Special Thanks

Alan Agius, Keen Yee Liau, Jesús, Emmanuel Demey

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

UnhandledPromiseRejectionWarning: Error: Multiple root routing modules found

I am trying to do npx angular-prerender after I doing a successful ng build

I got this error:
PS C:\Development\xyz\ClientApps> npx angular-prerender
(node:1384) UnhandledPromiseRejectionWarning: Error: Multiple root routing modules found C:\Development\xyz\ClientApps\libs\shared\src\lib\shared-routing.module.ts, C:\Development\xyz\ClientApps\apps\website\src\app\app.module.ts, C:\Development\xyz\ClientApps\libs\about\src\lib\about-routing.module.ts, C:\Development\xyz\ClientApps\libs\agent\src\lib\agent-routing.module.ts, C:\Development\xyz\ClientApps\libs\camp\src\lib\camp-routing.module.ts, C:\Development\xyz\ClientApps\libs\flight\src\lib\flight-routing.module.ts, C:\Development\xyz\ClientApps\libs\game\src\lib\game-routing.module.ts, C:\Development\xyz\ClientApps\libs\giftcard\src\lib\gift-card-routing.module.ts, C:\Development\xyz\ClientApps\libs\home\src\lib\home-routing.module.ts, C:\Development\xyz\ClientApps\libs\profile\src\lib\profile-routing.module.ts, C:\Development\xyz\ClientApps\libs\trip\src\lib\trip-routing.module.ts
at findRootModule (C:\Development\xyz\ClientApps\node_modules\guess-parser\dist\guess-parser\index.js:412:15)
at exports.parseRoutes (C:\Development\xyz\ClientApps\node_modules\guess-parser\dist\guess-parser\index.js:575:31)
at prerender (C:\Development\xyz\ClientApps\node_modules\angular-prerender\build\node\functions\prerender.js:89:54)
(node:1384) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:1384) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with
a non-zero exit code.

I have 3 angular apps and several libraries, but I tried to prerender the default app.

here are my configurations:
ng --version

 _                      _                 ____ _     ___ 
/ \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|

/ △ \ | '_ \ / | | | | |/ _ | '__| | | | | | |
/ ___ | | | | (| | || | | (| | | | || | | |
// __| ||_, |_,||_,|| _|||
|___/

Angular CLI: 8.3.6
Node: 12.4.0
OS: win32 x64
Angular: 8.2.8
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... platform-server, router, service-worker, upgrade

Package Version

@angular-devkit/architect 0.803.3
@angular-devkit/build-angular 0.803.6
@angular-devkit/build-ng-packagr 0.803.6
@angular-devkit/build-optimizer 0.803.6
@angular-devkit/build-webpack 0.803.6
@angular-devkit/core 8.3.6
@angular-devkit/schematics 8.3.6
@angular/cdk 8.2.2
@angular/cli 8.3.6
@angular/http 7.2.15
@angular/material 8.2.2
@angular/material-moment-adapter 8.2.2
@angular/pwa 0.803.6
@ngtools/webpack 8.3.6
@nguniversal/common 8.1.1
@nguniversal/express-engine 8.1.1
@nguniversal/module-map-ngfactory-loader 8.1.1
@schematics/angular 8.3.6
@schematics/update 0.803.6
ng-packagr 5.5.1
rxjs 6.5.3
typescript 3.5.3
webpack 4.39.2

An in-range update of tsconfig-holy-grail is breaking the build 🚨

The devDependency tsconfig-holy-grail was updated from `10.0.9` to `10.0.10`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 9 commits.

b89c36e 10.0.10
2de28ac fix(package): update mocha to version 6.2.0
801154f fix(package): update load-grunt-config to version 2.0.1
c03d381 fix(package): update husky to version 3.0.1
6c8b50d fix(package): update eslint-config-holy-grail to version 38.0.3
9af0268 fix(package): update eslint to version 6.1.0
ff2412a fix(package): update cz-conventional-changelog to version 3.0.2
2794afb fix(package): update commitizen to version 4.0.3
a88de23 fix(package): update @types/node to version 12.6.8

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @angular-devkit/core is breaking the build 🚨

The dependency @angular-devkit/core was updated from `7.1.4` to `7.2.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular-devkit/core is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build failed.

Release Notes for v7.2.0

Commits

@angular/cli (7.2.0)
Commit	Description	Notes
	initial minimal BEP support
	update optimization options
	Added support for multiselect list prompt (#13031)
	add warning for overriding flags in arguments	[Closes #12948]
	add `resourcesOutputPath` to schema
	remove redundant period in deprecation warning
	show full path to project definition when already exists	[Closes #13138]
	pass arguments to all targets	[Closes #10657] [Closes #10656] [Closes #11005]
	handle case senstive aliases	[Closes #12780]
	improve architect command project parsing
@schematics/angular (7.2.0)
Commit	Description	Notes
	add support for TypeScript 3.2 and Angular 7.2.0-rc.0
	add `lintFix` to several other schematics	[Closes #12894] [Closes #6272]
	consistent naming of options and arguments that do the same thing	[Closes #12784]
	add .history directory to gitignore
	wrapping bootstrap code in a DOMContentLoaded in variable declaration	[Closes #13042]
	set `optimization` and `sourceMap` in universal production config	[Closes #12541] [Closes #12940]
	cannot create pipe in sub-directory if module is in different sub-directory	[Closes #13182]
	import zone related flags in other files	[Closes #12886]
	let tslint resolve codelyzer (#13101)	[Closes #13101] [Closes #13100]
	add providers into providers metadata but not inner Object with ut. (#13081)
@angular-devkit/schematics-cli (0.12.0)
Commit	Description	Notes
	add prompt support using Inquirer
@angular-devkit/build-angular (0.12.0)
Commit	Description	Notes
	fine grain settings for optimization
	fine grain settings for sourceMaps (#13062)	[Closes #7527]
	add option to allow outputting css resources to a different folder
	resolve project root for fork process	[Closes #13113]
	remove circular dependencies warnings in ngfactory files	[Closes #11135]
	remove invalid colors option of ProgressPlugin
	output non human readable lint result	[Closes #13173]
	lint non human readable formatters produces invalid output	[Closes #12674]
	remove `skipAppShell` as it has no effect in browser builder	[Closes #11478]
@angular-devkit/core (7.2.0)
Commit	Description	Notes
	Jobs API added
	add DeepReadonly<> and Readwrite<> types
	add a new JsonSchema type
	add next() to Logger
@ngtools/webpack (7.2.0)
Commit	Description	Notes
	support directly loading component templates
	`import as` results in the alias being undefined with Typescript 3.2	[Closes #13212]
	avoid checking watchMode in environment hook
	files are not being updated when using `allowJs` or `resolveJsonModule` (#13089)	[Closes #13076] [Closes #12964]
	cleanup resources after modules are loaded (#12994)
@schematics/schematics (0.12.0)
Commit	Description	Notes
	add support for TypeScript 3.2
@schematics/update (0.12.0)
Commit	Description	Notes
	add packageGroup version map support	[Closes #13015]
	add initial verbose option (#12995)
	ignore npm 404 error
	only set registry option when used
	replace environment variables in npm/yarn rc

Special Thanks

Alan Agius, Hans Larsen, Charles Lyding, Renovate Bot, Alex Eagle, Judy Bogart, Cédric Exbrayat, Alan, Hayden Berge, Amadou Sall, Filipe Silva, Tiago Temporin, mhartington, James George, jonwrede, Minko Gechev, JiaLiPassion, Pascal Honegger, Michael Nahkies, Vikram Subramanian, 赵正阳, Mathou54, Krishna Mohan, Michael O'Keefe, Carlo Dapor, Keen Yee Liau

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint-config-holy-grail is breaking the build 🚨

The devDependency eslint-config-holy-grail was updated from `38.0.2` to `38.0.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 13 commits.

f9fde56 38.0.3
7cb4b81 test: explicitily name file
d7e4a7a fix(package): update eslint-plugin-unicorn to version 10.0.0
2d3a87a fix(package): update eslint-plugin-import to version 2.18.2
ab112ac fix(package): update eslint to version 6.1.0
cfb1c96 fix(package): update mocha to version 6.2.0
c99539b fix(package): update load-grunt-config to version 2.0.1
0c176ab fix(package): update husky to version 3.0.1
cbb015b fix(package): update cz-conventional-changelog to version 3.0.2
5f01718 fix(package): update commitizen to version 4.0.3
07dbdba fix(package): update @commitlint/config-angular to version 8.1.0
6fce751 fix(package): update @commitlint/cli to version 8.1.0
1bd37db fix(package): update lockfile

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

duplicate app state in prerendered page

hi @chrisguttandin, I am able to use this package to successfully, the only thing is that I get duplicate data states for example, I have <script id="serverApp-state"></script> injected twice where serverApp is the appId assigned to BrowserModule.withServerTransition({ appId: 'serverApp' }), and as a result, Browser transfer state mechanisms do not work. is this something that the package does intentionally and how can I get around it.

nb. when I delete the extra <script id="serverApp-state"></script>, transfer state works fine.

An in-range update of eslint is breaking the build 🚨

The devDependency eslint was updated from `6.2.1` to `6.2.2`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ Travis CI - Branch: The build failed.

Release Notes for v6.2.2

0e0b784 Upgrade: espree@^6.1.1 (#12158) (Kevin Partington)
04e859f Sponsors: Sync README with website (ESLint Jenkins)
34783d1 Sponsors: Sync README with website (ESLint Jenkins)
b809e72 Docs: Update README team and sponsors (ESLint Jenkins)

Commits

The new version differs by 6 commits.

ca658fb 6.2.2
3ed9f76 Build: changelog update for 6.2.2
0e0b784 Upgrade: espree@^6.1.1 (#12158)
04e859f Sponsors: Sync README with website
34783d1 Sponsors: Sync README with website
b809e72 Docs: Update README team and sponsors

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

"Multiple root routing modules" error when one lazy loading module is loaded from another

Hi @chrisguttandin
Any help you can give would be appreciated

Error: Multiple root routing modules found /home/bryce/temp/prerender-multilevel-lazyload/src/app/lazy-level2/lazy-level2-routing.module.ts, /home/bryce/temp/prerender-multilevel-lazyload/src/app/app.module.ts

I've created an example app to demonstrate this.

git clone https://github.com/helix46/prerender-multilevel-lazyload.git
cd prerender-multilevel-lazyload
npm i
ng build
ng run prerender-multilevel-lazyload:server
npx angular-prerender

guess-parser recognises that the first level lazy loaded routing module is not root, but does not see that the second level lazy loaded routing module is loaded by import from the first and is not root

Angular CLI: 9.0.6
Node: 12.16.1
OS: linux x64

An in-range update of tsconfig-holy-grail is breaking the build 🚨

The devDependency tsconfig-holy-grail was updated from `10.0.1` to `10.0.2`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 4 commits.

2637f73 10.0.2
58fb9d9 fix(package): update @types/node to version 12.0.3
9658f63 fix(package): update eslint-config-holy-grail to version 36.0.3
f6cf891 fix(package): update eslint-config-holy-grail to version 36.0.2

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Error generating static site when adding lazy loading routes

Error

Steps to reproduce

npx @angular/cli new ng-static --routing
ng generate universal --client-project ng-static
Create lazy route
ng build
ng run ng-static:server
npx angular-prerender

Feature request: add support for `--exclude-routes *`

Hi.

I'm using @gilsdav/ngx-translate-router.
So I have to manualy exclude each route by adding it to --exclude-routes.

Is it possible to either add the support of wildcard exclude or the propper parsing that can handle localized routes?

An in-range update of core-js is breaking the build 🚨

The dependency core-js was updated from `3.4.6` to `3.4.7`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

core-js is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build errored.

Release Notes for 3.4.7 - 2019.12.03

Fixed an NPM publishing issue

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @types/yargs is breaking the build 🚨

The devDependency @types/yargs was updated from `12.0.1` to `12.0.2`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ Travis CI - Branch: The build failed.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of yargs is breaking the build 🚨

The dependency yargs was updated from `13.2.2` to `13.2.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

yargs is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build errored.

Commits

The new version differs by 14 commits.

a6e67f1 chore(release): 13.2.4
fc13476 chore: update standard-verison dependency
bf46813 fix(i18n): rename unclear 'implication failed' to 'missing dependent arguments' (#1317)
a3a5d05 docs: fix a broken link to MS Terminology Search (#1341)
b4f8018 build: add .versionrc that hides test/build
0c39183 chore(release): 13.2.3
08e0746 chore: update deps (#1340)
843e939 docs: make --no- boolean prefix easier to find in the docs (#1338)
84cac07 docs: restore removed changelog of v13.2.0 (#1337)
b20db65 fix(deps): upgrade cliui for compatibility with latest chalk. (#1330)
c294d1b test: accept differently formatted output (#1327)
ac3f10c chore: move .hbs templates into .js to facilitate webpacking (#1320)
0295132 fix: address issues with dutch translation (#1316)
9f2468e doc: clarify parserConfiguration object structure (#1309)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of guess-parser is breaking the build 🚨

The dependency guess-parser was updated from `0.3.9` to `0.3.10`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

guess-parser is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 3 commits.

90c4146 v0.3.10
902b6d4 Introduce exclude file option in the angular router (#177)
d9cb0a9 Introduce support to absolute project URLs in the angular parser (#173)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Add changelog

An in-range update of tslint-config-holy-grail is breaking the build 🚨

The devDependency tslint-config-holy-grail was updated from `39.0.3` to `39.0.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 2 commits.

5c56b98 39.0.4
0073404 fix: simple define codelyzer as string

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

chrisguttandin / angular-prerender Goto Github PK

angular-prerender's People

Stargazers

Watchers

Forkers

angular-prerender's Issues

The devDependency eslint-config-holy-grail was updated from 46.0.14 to 46.0.15.

The devDependency husky was updated from 3.0.1 to 3.0.2.

The devDependency husky was updated from 4.0.8 to 4.0.9.

The devDependency tslint-config-holy-grail was updated from 44.0.6 to 44.0.7.

The dependency @angular-devkit/core was updated from 7.2.1 to 7.2.2.

Commits

@schematics/angular (7.2.2)

@angular-devkit/build-angular (0.12.2)

@angular-devkit/build-optimizer (0.12.2)

@angular-devkit/core (7.2.2)

@ngtools/webpack (7.2.2)

@schematics/update (0.12.2)

Special Thanks

The devDependency tslint-config-holy-grail was updated from 37.0.0 to 37.0.1.

The dependency @angular-devkit/core was updated from 8.1.2 to 8.1.3.

The dependency @angular-devkit/core was updated from 8.2.2 to 8.3.0.

Commits

@schematics/angular (8.3.0)

Special Thanks

The devDependency commitizen was updated from 3.0.2 to 3.0.3.

3.0.3 (2018-10-19)

Bug Fixes

The devDependency tsconfig-holy-grail was updated from 6.0.8 to 6.0.9.

The devDependency @types/yargs was updated from 13.0.0 to 13.0.1.

There have been updates to the commitlint monorepo:

The devDependency tsconfig-holy-grail was updated from 10.0.26 to 10.0.27.

The dependency @angular-devkit/core was updated from 8.3.24 to 8.3.25.

Commits

Misc

@angular-devkit/build-angular (0.803.25)

Special Thanks

The devDependency tslint-config-holy-grail was updated from 36.0.3 to 36.0.4.

Version 0.7.5 of @angular-devkit/core was just published.

The dependency guess-parser was updated from 0.4.12 to 0.4.13.

The dependency @angular-devkit/core was updated from 7.2.3 to 7.2.4.

The dependency @angular-devkit/core was updated from 7.0.5 to 7.0.6.

Commits

@angular/cli (7.0.6)

@schematics/angular (7.0.6)

@angular-devkit/core (7.0.6)

@ngtools/webpack (7.0.6)

Special Thanks

Package Version

The devDependency tsconfig-holy-grail was updated from 10.0.9 to 10.0.10.

The dependency @angular-devkit/core was updated from 7.1.4 to 7.2.0.

Commits

@angular/cli (7.2.0)

@schematics/angular (7.2.0)

@angular-devkit/schematics-cli (0.12.0)

@angular-devkit/build-angular (0.12.0)

@angular-devkit/core (7.2.0)

@ngtools/webpack (7.2.0)

@schematics/schematics (0.12.0)

@schematics/update (0.12.0)

Special Thanks

The devDependency eslint-config-holy-grail was updated from 38.0.2 to 38.0.3.

The devDependency eslint was updated from 6.2.1 to 6.2.2.

The devDependency tsconfig-holy-grail was updated from 10.0.1 to 10.0.2.

The dependency core-js was updated from 3.4.6 to 3.4.7.

The devDependency @types/yargs was updated from 12.0.1 to 12.0.2.

The dependency yargs was updated from 13.2.2 to 13.2.4.

The dependency guess-parser was updated from 0.3.9 to 0.3.10.

The devDependency tslint-config-holy-grail was updated from 39.0.3 to 39.0.4.

Recommend Projects

Recommend Topics

Recommend Org

The devDependency eslint-config-holy-grail was updated from `46.0.14` to `46.0.15`.

The devDependency husky was updated from `3.0.1` to `3.0.2`.

The devDependency husky was updated from `4.0.8` to `4.0.9`.

The devDependency tslint-config-holy-grail was updated from `44.0.6` to `44.0.7`.

The dependency @angular-devkit/core was updated from `7.2.1` to `7.2.2`.

The devDependency tslint-config-holy-grail was updated from `37.0.0` to `37.0.1`.

The dependency @angular-devkit/core was updated from `8.1.2` to `8.1.3`.

The dependency @angular-devkit/core was updated from `8.2.2` to `8.3.0`.

The devDependency commitizen was updated from `3.0.2` to `3.0.3`.

The devDependency tsconfig-holy-grail was updated from `6.0.8` to `6.0.9`.

The devDependency @types/yargs was updated from `13.0.0` to `13.0.1`.

The devDependency tsconfig-holy-grail was updated from `10.0.26` to `10.0.27`.

The dependency @angular-devkit/core was updated from `8.3.24` to `8.3.25`.

The devDependency tslint-config-holy-grail was updated from `36.0.3` to `36.0.4`.

The dependency guess-parser was updated from `0.4.12` to `0.4.13`.

The dependency @angular-devkit/core was updated from `7.2.3` to `7.2.4`.

The dependency @angular-devkit/core was updated from `7.0.5` to `7.0.6`.

The devDependency tsconfig-holy-grail was updated from `10.0.9` to `10.0.10`.

The dependency @angular-devkit/core was updated from `7.1.4` to `7.2.0`.

The devDependency eslint-config-holy-grail was updated from `38.0.2` to `38.0.3`.

The devDependency eslint was updated from `6.2.1` to `6.2.2`.

The devDependency tsconfig-holy-grail was updated from `10.0.1` to `10.0.2`.

The dependency core-js was updated from `3.4.6` to `3.4.7`.

The devDependency @types/yargs was updated from `12.0.1` to `12.0.2`.

The dependency yargs was updated from `13.2.2` to `13.2.4`.

The dependency guess-parser was updated from `0.3.9` to `0.3.10`.

The devDependency tslint-config-holy-grail was updated from `39.0.3` to `39.0.4`.