rucken / core-nestjs

A simple application demonstrating the basic usage of permissions with NestJS (JWT, Passport, Facebook, Google+, User, Group, Permission)

rucken-core-nestjs

A simple application demonstrating the basic usage of permissions with NestJS (JWT, Passport, Facebook, Google+, User, Group, Permission) based on Rucken template

Screenshots

Features

• NestJS - a JS backend framework providing architecture out of the box with a syntax similar to Angular
• TypeORM - ORM for TypeScript and JavaScript (ES7, ES6, ES5). Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Server, Oracle, WebSQL databases.
• TypeScript - superset of JS which compiles to JS, providing compile-time type checking
• Passport - a popular library used to implement JavaScript authentication (Facebook, Google+)
• jsonwebtoken - a JavaScript json web tokens implementation by auth0
• @nrwl/schematics - Angular CLI power-ups for modern development, example usage: ng g @nrwl/schematics:node-app app-name --framework nestjs
• @nestjs/schematics - Nest architecture element generation based on Angular schematics, example usage: ng g @nestjs/schematics:library lib-name

Usage

• clone or fork repository git clone --recursive https://github.com/rucken/core-nestjs.git
• make sure you have node.js installed version 11+
• copy develop._env to develop.env and set environments for use (on Windows copy with IDE)
• run npm install to install project dependencies
• run npm run build to install project dependencies
• run npm run start:prod to fire up prod server (npm run start:dev - dev server)
• Open browser to http://localhost:5000/swagger

Demo

https://core-nestjs.rucken.ru - Application with Sqlite Database on VPS with Dokku

Users

• user with admin group: [email protected], password: 12345678
• user with user group: [email protected], password: 12345678
• user with user group: [email protected], password: 12345678

Swagger

• local: http://localhost:5000/swagger
• online: https://core-nestjs.rucken.ru/swagger
• apiKey template: JWT <token_generated_on_login>

Typedoc documentations

• local: http://localhost:5000/docs
• online: https://core-nestjs.rucken.ru/docs

Quick links

Frontend (with core)

@rucken/core - Core with Admin UI for web application maked on Angular7+ and Bootstrap3.

@rucken/todo - Core with UI for web todo application maked on Angular7+ and Bootstrap3.

Backend

@rucken/core-nestjs - A simple application demonstrating the basic usage of permissions with NestJS (JWT, Passport, Facebook, Google+, User, Group, Permission).

@rucken/todo-nestjs - A simple todo application with NestJS (Projects, Tasks, Statuses).

Mobile

@rucken/ionic - Admin UI for Ionic4 with Angular7+ mobile application.

@rucken/todo-ionic - Admin UI for Ionic4 with Angular7+ mobile todo application

Console

@rucken/cli - Console tools to create and build Angular7+ and NestJS application based on Rucken template

License

MIT

core-nestjs's Issues

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

The devDependency prettier was updated from 1.15.2 to 1.15.3.

🚨 View failing branch.

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

prettier 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 could not complete due to an error (Details).

---

Release Notes for 1.15.3

🔗 Changelog

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 🌴

feat: Add field=module_name to content_type and update all exists with migration

An in-range update of @nrwl/schematics is breaking the build 🚨

The devDependency @nrwl/schematics was updated from 7.6.0 to 7.6.1.

🚨 View failing branch.

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

@nrwl/schematics 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

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/supertest is breaking the build 🚨

The devDependency @types/supertest was updated from 2.0.6 to 2.0.7.

🚨 View failing branch.

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

@types/supertest 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 could not complete due to an error (Details).

---

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/jest is breaking the build 🚨

The devDependency @types/jest was updated from 23.3.6 to 23.3.7.

🚨 View failing branch.

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

@types/jest 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 could not complete due to an error (Details).

---

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 🌴

chore: Add check email is not null

as rucken/todo-nestjs#56

An in-range update of @nrwl/builders is breaking the build 🚨

The devDependency @nrwl/builders was updated from 7.6.0 to 7.6.1.

🚨 View failing branch.

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

@nrwl/builders 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 could not complete due to an error (Details).
• ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

---

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/node is breaking the build 🚨

The devDependency @types/node was updated from 10.9.4 to 10.10.0.

🚨 View failing branch.

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

@types/node 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

• ✅ deployment/now: Deployment has completed (Details).
• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

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 🌴

chore: Add check exists property "architect.build.options"

core-nestjs/ormconfig.js

Line 50 in ad1b5a4

`${lib[sourceRootKey] || lib.architect.build.options[sourceRootKey]}/**/migrations_entities/**/*.entity${entitiesExt}`

fix: Change dto on info to UserTokenDto

core-nestjs/libs/rucken/auth-nestjs/src/controllers/auth.controller.ts

Line 65 in ad1b5a4

return plainToClass(OutAccountDto, { user });

feat(files): Add file storage module

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The engines config in 1 of your package.json files was updated to the new Node.js version

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

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 🌴

Unit testing your services and controllers

Hello! I like the general setup of your project. I played a bit around with it and I asked myself how you would unit test your controllers and services (For example the auth.service) which has such a high amount of dependencies.

feat: Update to typeorm@next and move migrations to ts files and add support simple share its between applications and moduleds

fix: Create content type = "client", and move to it all used only in frontend

core-nestjs/libs/rucken/core-nestjs/src/migrations/1524199144534-FillFrontendData.ts

Line 29 in fb42b04

'read_themes-page': 'Can read themes page',

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

The devDependency @angular-devkit/build-angular was updated from 0.13.2 to 0.13.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/build-angular 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/appveyor/branch: AppVeyor build failed (Details).
• ✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).

---

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 🌴

fix(migrate): Create migrate from models

An in-range update of fastify-formbody is breaking the build 🚨

The dependency fastify-formbody was updated from 2.0.2 to 2.0.3.

🚨 View failing branch.

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

fastify-formbody 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 could not complete due to an error (Details).

---

Release Notes for v2.0.3

#29 - Next versions of this plugin will support Fastify ^2.0.0

Commits

The new version differs by 2 commits.

• d909018 2.0.3
• 6dca156 Add support notice to readme (#29)

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 @nestjs/common is breaking the build 🚨

The dependency @nestjs/common was updated from 5.3.6 to 5.3.7.

🚨 View failing branch.

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

@nestjs/common 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).

---

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 🌴

New feature suggest

I really like this repository.
If it have a dashboard like django admin is awesome!!
Do you have a plain to do it??
I think it will become a very useful library!!

fix: Update permissions of groups after modify any groups

fix: Update to correct work, and write error in index.html for work with him from spa

core-nestjs/src/libs/core/filters/custom-exception.filter.ts

Line 36 in 80a5efc

request.originalUrl.indexOf('/api/') !== 0 &&

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

The dependency @nestjs/core was updated from 5.3.6 to 5.3.7.

🚨 View failing branch.

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

@nestjs/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).

---

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 🌴

feat: Rename oauth_tokens_accesstokens to auth_tokens_accesstokens with migration

feat(front): Add new fronted

feat(ssr): Add support run with frontend over ssr

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

Version 3.1.1 of pm2 was just published.

Branch	Build failing 🚨
Dependency	pm2
Current Version	3.1.0
Type	devDependency

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

pm2 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 could not complete due to an error (Details).

---

Commits

The new version differs by 2 commits.

• 172d5ea chore: upgrade to 3.1.1
• 7b43fea hotfix: #3901 fix error when installing module

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/cli is breaking the build 🚨

The devDependency @angular/cli was updated from 7.3.2 to 7.3.3.

🚨 View failing branch.

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

@angular/cli 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/appveyor/branch: AppVeyor build failed (Details).
• ✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).

---

Release Notes for v7.3.3

Commits

@schematics/angular (7.3.3)
Commit	Description	Notes
	update karma to version 4	[Closes #13724]
	`findModuleFromOptions` not handling properly different casing in name	[Closes #13714]
	undefined is used as newProjectRoot when none is set	[Closes #13703]
	add file extensions to style prompt
	fixes issue that `ViewEncapsulation` is not being configured when provided	[Closes #13689]
@angular-devkit/build-angular (0.13.3)
Commit	Description	Notes
	improve webpack loader resolution
	minimum threshold

---

Special Thanks

Alan Agius, Amadou Sall, Alan, Charles Lyding, hrocha16

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 🌴

feat(db): Add deploy to Postgres on heroku

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

The dependency pg was updated from 7.6.1 to 7.7.0.

🚨 View failing branch.

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

pg 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 could not complete due to an error (Details).

---

Commits

The new version differs by 3 commits.

• f52a0fe Bump version
• 77866d0 Update changelog
• eb076db Add configurable query timeout (#1760)

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/schematics is breaking the build 🚨

The devDependency @angular-devkit/schematics was updated from 7.3.2 to 7.3.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/schematics 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/appveyor/branch: AppVeyor build failed (Details).
• ✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).

---

Release Notes for v7.3.3

Commits

@schematics/angular (7.3.3)
Commit	Description	Notes
	update karma to version 4	[Closes #13724]
	`findModuleFromOptions` not handling properly different casing in name	[Closes #13714]
	undefined is used as newProjectRoot when none is set	[Closes #13703]
	add file extensions to style prompt
	fixes issue that `ViewEncapsulation` is not being configured when provided	[Closes #13689]
@angular-devkit/build-angular (0.13.3)
Commit	Description	Notes
	improve webpack loader resolution
	minimum threshold

---

Special Thanks

Alan Agius, Amadou Sall, Alan, Charles Lyding, hrocha16

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 conventional-changelog-cli is breaking the build 🚨

The devDependency conventional-changelog-cli was updated from 2.0.5 to 2.0.7.

🚨 View failing branch.

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

conventional-changelog-cli 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 could not complete due to an error (Details).

---

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 webpack is breaking the build 🚨

Version 4.18.0 of webpack was just published.

Branch	Build failing 🚨
Dependency	webpack
Current Version	4.17.3
Type	devDependency

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

webpack 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 could not complete due to an error (Details).

---

Release Notes

v4.18.0

Features

• Upgrade webassemblyjs dependency

Commits

The new version differs by 12 commits.

• ee7d948 4.18.0
• de85978 Merge pull request #7732 from xtuc/chore-bump-webassemblyjs11
• 4e02cac chore: bump webassemblyjs
• 52e1630 bump webassemblyjs
• e0e0061 Merge branch 'master' into chore-bump-webassemblyjs11
• c9d6ec1 feat: remove wasm-opt
• 075208d fix: merging
• 38c3403 Merge remote-tracking branch 'upstream/master' into chore-bump-webassemblyjs11
• 8214d56 chore: bump webassemblyjs
• 59114c1 chore: bump webassemblyjs
• b310b9b feat: remove LEB128 opt
• f744c4a chore: bump webassemblyjs 1.6.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 🌴

chore: Add screenshots with comments

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

The devDependency tslint-config-prettier was updated from 1.16.0 to 1.17.0.

🚨 View failing branch.

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

tslint-config-prettier 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 could not complete due to an error (Details).

---

Release Notes for v1.17.0

1.17.0 (2018-11-27)

Features

• Switch to Yarn instead of npm (537a7ad)

Commits

The new version differs by 19 commits.

• d336552 Merge pull request #238 from lipis/yarn
• 537a7ad feat: Switch to Yarn instead of npm
• 6c38ddc chore(deps-dev): bump semantic-release from 15.12.0 to 15.12.2
• 9c13ec5 chore(deps-dev): bump vrsource-tslint-rules from 5.8.2 to 5.8.3 (#237)
• 2e1fd17 chore(deps-dev): bump tslint-immutable from 4.9.1 to 5.0.0 (#235)
• 7540e0b chore(deps-dev): bump ts-jest from 23.10.4 to 23.10.5 (#233)
• d285f6a Merge pull request #218 from prettier/readme
• c77472a Merge pull request #220 from prettier/dependabot/npm_and_yarn/semantic-release-15.12.0
• 0dc80a1 chore(deps-dev): bump typescript from 3.0.3 to 3.1.6 (#231)
• 168588a chore(deps-dev): bump tslint-misc-rules from 3.5.0 to 3.5.1 (#229)
• c53a625 chore(deps-dev): bump @types/prettier from 1.13.2 to 1.15.1 (#230)
• 4bb4e9b docs(readme): add link to conflicting rules list to README (#228)
• 9d573c6 chore(deps-dev): bump codelyzer from 4.1.0 to 4.5.0 (#225)
• 983bc18 chore: npm audit fix (#224)
• 9bda093 chore(deps-dev): bump semantic-release from 15.1.7 to 15.12.0

There are 19 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 🌴

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

The dependency typeorm was updated from 0.2.8 to 0.2.9.

🚨 View failing branch.

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

typeorm 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 could not complete due to an error (Details).

---

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 devDependency @angular-devkit/core was updated from 7.3.2 to 7.3.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 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/appveyor/branch: AppVeyor build failed (Details).
• ✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).

---

Release Notes for v7.3.3

Commits

@schematics/angular (7.3.3)
Commit	Description	Notes
	update karma to version 4	[Closes #13724]
	`findModuleFromOptions` not handling properly different casing in name	[Closes #13714]
	undefined is used as newProjectRoot when none is set	[Closes #13703]
	add file extensions to style prompt
	fixes issue that `ViewEncapsulation` is not being configured when provided	[Closes #13689]
@angular-devkit/build-angular (0.13.3)
Commit	Description	Notes
	improve webpack loader resolution
	minimum threshold

---

Special Thanks

Alan Agius, Amadou Sall, Alan, Charles Lyding, hrocha16

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 🌴

feat: Add prefix "core_" to all tables usage in core module

feat(mongo): Add repository services work with MongoDB

An in-range update of @nrwl/nx is breaking the build 🚨

The dependency @nrwl/nx was updated from 7.6.0 to 7.6.1.

🚨 View failing branch.

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

@nrwl/nx 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

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 @nestjs/platform-express is breaking the build 🚨

The dependency @nestjs/platform-express was updated from 6.1.1 to 6.2.0.

🚨 View failing branch.

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

@nestjs/platform-express 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 passed (Details).
• ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

---

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 conventional-recommended-bump is breaking the build 🚨

The devDependency conventional-recommended-bump was updated from 4.0.1 to 4.0.3.

🚨 View failing branch.

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

conventional-recommended-bump 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 could not complete due to an error (Details).

---

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 🌴

feat: Add scaffold by fields, entity properties for backend and model properties for frontend

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

The devDependency nodemon was updated from 1.18.5 to 1.18.6.

🚨 View failing branch.

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

nodemon 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 could not complete due to an error (Details).

---

Release Notes for v1.18.6

1.18.6 (2018-11-05)

Bug Fixes

• restart on change for non-default signals (#1409) (#1430) (521eb1e)

Commits

The new version differs by 1 commits.

• 521eb1e fix: restart on change for non-default signals (#1409) (#1430)

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 @nestjs/testing is breaking the build 🚨

The devDependency @nestjs/testing was updated from 5.4.0 to 5.4.1.

🚨 View failing branch.

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

@nestjs/testing 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 could not complete due to an error (Details).

---

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 🌴

feat(service): Add sort query parameter

WARNING ! NPM 404 because of security incident

Hey there,
this project is not installable because of the event-stream dependency.
[ several related greenkeeper issues exist ]

Also there should be a note for people used it in the past that they must update their package.json :

The malicious subdependency came with "npm-run-all": "^4.1.3" which should be upgraded to "npm-run-all": "^4.1.5" to make it work again – see these issues in npm-run-all

The npm post - “After triaging the malware, npm Security responded by removing flatmap-stream and [email protected] from the Registry and taking ownership of the event-stream package to prevent further abuse.”

See also
https://www.theregister.co.uk/2018/11/26/npm_repo_bitcoin_stealer/
https://medium.com/intrinsic/compromised-npm-package-event-stream-d47d08605502

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

The dependency typeorm was updated from 0.2.13 to 0.2.14.

🚨 View failing branch.

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

typeorm 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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/architect is breaking the build 🚨

The devDependency @angular-devkit/architect was updated from 0.13.2 to 0.13.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/architect 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/appveyor/branch: AppVeyor build failed (Details).
• ✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).

---

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 dotenv is breaking the build 🚨

The dependency dotenv was updated from 6.1.0 to 6.2.0.

🚨 View failing branch.

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

dotenv 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 could not complete due to an error (Details).

---

Commits

The new version differs by 4 commits.

• e1e7d57 6.2.0
• 1eacd53 add support for preload configuration via env vars (#355)
• 1f84ba1 add TypeScript types (#345)
• 194c98e Fix appveyor repo badge url in readme (#347)

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 🌴