build(deps): bump picomatch, @nestjs/cli and @nestjs/schematics Bumps [picomatch](https://github.com/micromatch/picomatch) to 2.3.2 and updates ancestor dependencies [picomatch](https://github.com/micromatch/picomatch), [@nestjs/cli](https://github.com/nestjs/nest-cli) and [@nestjs/schematics](https://github.com/nestjs/schematics). These dependencies need to be updated together. Updates `picomatch` from 2.3.1 to 2.3.2 - [Release notes](https://github.com/micromatch/picomatch/releases) - [Changelog](https://github.com/micromatch/picomatch/blob/master/CHANGELOG.md) - [Commits](https://github.com/micromatch/picomatch/compare/2.3.1...2.3.2) Updates `@nestjs/cli` from 10.3.2 to 10.4.9 - [Release notes](https://github.com/nestjs/nest-cli/releases) - [Commits](https://github.com/nestjs/nest-cli/compare/10.3.2...10.4.9) Updates `@nestjs/schematics` from 10.1.1 to 10.2.3 - [Release notes](https://github.com/nestjs/schematics/releases) - [Commits](https://github.com/nestjs/schematics/compare/10.1.1...10.2.3) --- updated-dependencies: - dependency-name: picomatch dependency-version: 2.3.2 dependency-type: indirect - dependency-name: "@nestjs/cli" dependency-version: 10.4.9 dependency-type: direct:development - dependency-name: "@nestjs/schematics" dependency-version: 10.2.3 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
A demo shows how to use nest-authz to implement role-based access control.
$ npm install
# development $ npm run start # watch mode $ npm run start:dev # production mode $ npm run start:prod
Open http://localhost:3000/api to see api. The api uses Bear auth schema, so if you want to access protected api, you should click the Authorize button and set Bearer yourjwttoken after login.
# unit tests $ npm run test