-
Updated
Jan 6, 2022 - TypeScript
Nest

Nest (NestJS) is a framework for building efficient, scalable Node.js server-side applications. It uses progressive JavaScript, is built with and fully supports TypeScript (yet still enables developers to code in pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).
Nest provides an out-of-the-box application architecture which allows developers and teams to create highly testable, scalable, loosely coupled, and easily maintainable applications.
Here are 4,081 public repositories matching this topic...
-
Updated
Jan 1, 2022
-
Updated
Jan 5, 2022 - TypeScript
Improve auth guard tests coverage.
add new tests and improve existing ones.
Auth guard path: ./packages/amplication-server/src/guards/gql-auth.guard.ts
Auth guard tests path: ./packages/amplication-server/src/guards/gql-auth.guard.spec.ts
We use jest
for tests and jest-mock-extended
for mocking.
-
Updated
Sep 4, 2020 - JavaScript
-
Updated
Dec 7, 2021 - TypeScript
I've read the docs, and it seems you can pass through knex
instances, but I didn't see if it supports SQLite3 - could you clarify please?
-
Updated
Jan 5, 2022 - TypeScript
-
Updated
Jan 5, 2022 - TypeScript
A recipe with Mocha
Clone the example app, only use Mocha instead of Jest
Before picking this issue, it's recommended to have a short tech planning chat here and only then upon sync to get up to speed.
Enrich our DB model
-
Updated
Oct 6, 2021 - TypeScript
Describe the bug
When I want to add staticly <Menu.Item>
on my CustomSider. useMenu
returns selectedKey as "notfound" but it should return the current location pathname. In this way, i can manage selected menu item with their key name.
Expected behavior
When useMenu
cannot find the resource, it should return location pathname.
**Desktop (please complete the following informa
Create a Wiki
It might be nice to have a Wiki set up to help people better understand the overall idea of the repository. Anyone is free to help out with this
-
Updated
Mar 24, 2021 - Vue
-
Updated
Dec 19, 2020
-
Updated
Jan 5, 2022 - TypeScript
-
Updated
Oct 18, 2021 - TypeScript
-
Updated
Jan 5, 2022 - TypeScript
-
Updated
Nov 26, 2021 - TypeScript
-
Updated
Jan 5, 2022 - TypeScript
-
Updated
Jan 5, 2022 - TypeScript
-
Updated
Jan 4, 2022 - TypeScript
-
Updated
Dec 22, 2021 - TypeScript
-
Updated
Dec 29, 2021 - TypeScript
Created by NestJS
Released May 14, 2017
Latest release about 1 month ago
- Repository
- nestjs/nest
- Website
- nestjs.com
Version Information
Latest
Environment
MacOS
What is the expected behaviour?
Events should be classified based on route
What is the current behaviour?
Events are spread across components, instead we need a single place for all keyboard events, and segregation between
global events
/route events
+ option to override global events if on specific route + option to over