kandi background

typeorm | Supports MySQL , PostgreSQL , MariaDB , SQLite , MS SQL Server | Object-Relational Mapping library

by typeorm TypeScript Version: 0.3.11 License: MIT

by typeorm TypeScript Version: 0.3.11 License: MIT

kandi X-RAY | typeorm Summary

typeorm is a TypeScript library typically used in Utilities, Object-Relational Mapping applications. typeorm has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

TypeORM is an ORM that can run in NodeJS, Browser, Cordova, PhoneGap, Ionic, React Native, NativeScript, Expo, and Electron platforms and can be used with TypeScript and JavaScript (ES5, ES6, ES7, ES8). Its goal is to always support the latest JavaScript features and provide additional features that help you to develop any kind of application that uses databases - from small applications with a few tables to large scale enterprise applications with multiple databases. TypeORM supports both Active Record and Data Mapper patterns, unlike all other JavaScript ORMs currently in existence, which means you can write high quality, loosely coupled, scalable, maintainable applications the most productive way. TypeORM is highly influenced by other ORMs, such as Hibernate, Doctrine and Entity Framework.

Support

Support

Quality

Quality

Security

Security

License

License

Reuse

Reuse

kandi-support Support

typeorm has a medium active ecosystem.
It has 30307 star(s) with 5647 fork(s). There are 357 watchers for this library.
There were 4 major release(s) in the last 6 months.
There are 1787 open issues and 5465 have been closed. On average issues are closed in 270 days. There are 62 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of typeorm is 0.3.11

typeorm Support

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

typeorm Support

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

quality kandi Quality

typeorm has 0 bugs and 0 code smells.

typeorm Quality

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

typeorm Quality

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

security Security

typeorm has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
typeorm code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.

typeorm Security

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

typeorm Security

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

license License

typeorm is licensed under the MIT License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.

typeorm License

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

typeorm License

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

build Reuse

typeorm releases are available to install and integrate.
Installation instructions, examples and code snippets are available.
It has 9 lines of code, 0 functions and 2703 files.
It has low code complexity. Code complexity directly impacts maintainability of the code.

typeorm Reuse

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

typeorm Reuse

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample Here

Get all kandi verified functions for this library.

Get all kandi verified functions for this library.

typeorm Key Features

Supports both DataMapper and ActiveRecord (your choice).

Entities and columns.

Database-specific column types.

Entity manager.

Repositories and custom repositories.

Clean object relational model.

Associations (relations).

Eager and lazy relations.

Uni-directional, bi-directional and self-referenced relations.

Supports multiple inheritance patterns.

Cascades.

Indices.

Transactions.

Migrations and automatic migrations generation.

Connection pooling.

Replication.

Using multiple database connections.

Working with multiple databases types.

Cross-database and cross-schema queries.

Elegant-syntax, flexible and powerful QueryBuilder.

Left and inner joins.

Proper pagination for queries using joins.

Query caching.

Streaming raw results.

Logging.

Listeners and subscribers (hooks).

Supports closure table pattern.

Schema declaration in models or separate configuration files.

Connection configuration in json / xml / yml / env formats.

Supports MySQL / MariaDB / Postgres / CockroachDB / SQLite / Microsoft SQL Server / Oracle / SAP Hana / sql.js.

Supports MongoDB NoSQL database.

Works in NodeJS / Browser / Ionic / Cordova / React Native / NativeScript / Expo / Electron platforms.

TypeScript and JavaScript support.

ESM and CommonJS support.

Produced code is performant, flexible, clean and maintainable.

Follows all possible best practices.

CLI.

typeorm Examples and Code Snippets

Community Discussions

Trending Discussions on typeorm

TypeORM insert row with foreign key
How to reference only one entity in a one-to-many relationship in TypeORM
What is the question mark for next to TypeScript arg when its GraphQL arg indicates nullable true?
Validation Error: Using global entity manager instance methods for context specific actions is disallowed
TypeORM composite foreign key
Can I abort DB operation / transaction in TypeORM using AbortSignal?
TypeORM Inner Join Same Table
npm ERESOLVE unable to resolve dependency tree NestJs Passport
Docker NodeJS app cant connect to postgres database
Mock bcrypt module module in Nest.js

Trending Discussions on typeorm

QUESTION

TypeORM insert row with foreign key

Asked 2022-Mar-07 at 04:01

I have a @OneToMany relation between
Chatroom < 1 ---- M > Messages
And the problem that I have is, whenever I try to insert a Message (or bulk of Messages), The foreign key for ChatRoom is null.
In addition, I'm uploading my setup.

@Entity("messages")
export class Message {

    @PrimaryColumn()
    id: string;

    @ManyToOne(() => ChatRoom, chatroom => chatroom.messages)
    chatRoom: ChatRoom | undefined

    @Column({nullable: false})
    message: string;

    @Column({nullable: false})
    receiver: string;

    @Column({nullable: false})
    created_utc: Date;
}

@Entity("chatrooms")
export class ChatRoom {

    @PrimaryColumn()
    id: string;

    @OneToMany(() => Message, message => message.chatRoom, {
        cascade: ["insert", "remove"]
    })
    @JoinColumn({name: 'id'})
    messages: Message[];

    @Column()
    last_msg: string;

    @Column()
    last_msg_created_utc: Date;

    @Column()
    num_messages: number;

    @Column()
    num_replies: number;

    @Column()
    seen: boolean;

}

Problem:

When trying to create a bulk insert on many messages, I can notice that the query is not setting the foreign key any value, but NULL.

The Message json that I'm trying to insert:

{
 id: '1',
 message: 'text',
 receiver: 'someone',
 created_utc: 'utc date...',
 chatRoomId: '123' -> chat room id exists 
}

the query looks like this :
(this query is for single insert not bulk, but it goes the same for bulk)
INSERT INTO "messages"("id", "message", "receiver", "created_utc", "chatRoomId") VALUES ($1, $2, $3, $4, DEFAULT) -- PARAMETERS: [" bJU7","Zdravo test","kompir_zomba","2021-
09-05T09:53:54.693Z"]

This tells me that chatRoomId is not even taken into consideration when inserting the rows. The table looks as following

The Typeorm insert query that I use to insert Messages

@InjectRepository(Message) private messageRepository: Repository<Message>
.....

    this.messageRepository.save(message);

Anyone has any idea how to proceed with this ?

ANSWER

Answered 2021-Sep-05 at 10:54

I have faced a similar issue with TypeORM when working on a NestJS project.

Reason:

The issue is happening because you don't have any chatRoomId field defined in your Message Entity (class Message). So, when TypORM maps your message data with the Message entity, it doesn't set the chatRoomId.

Solutions:

There are two solutions to fix this problem.

You can add the chatRoomId field in your Message entity and now you will be able to send the field when saving the message data.

e.g.

@Column({type: "uuid"}) // <- Assuming that your primary key type is UUID (OR you can have "char")
chatRoomId: string;

Now, usually you would not need to create a migration for this since this field already exists in the database table.

The other way is to pass an instance of ChatRoom entity to the message object when saving it.

You can, first, find the chat room using its ID and then pass it in the message object.

Your final message object should look like this:

{
 id: '1',
 message: 'text',
 receiver: 'someone',
 created_utc: 'utc date...',
 chatRoom: chatRoomData // <-- Assuming that chatRoomData contains the ChatRoom entity
}

Source https://stackoverflow.com/questions/69062374

QUESTION

What is the question mark for next to TypeScript arg when its GraphQL arg indicates nullable true?

Asked 2022-Feb-19 at 13:37

// image.entity.ts

import { Field, ObjectType } from '@nestjs/graphql';
import {
  Column,
  DeleteDateColumn,
  Entity,
  PrimaryGeneratedColumn,
} from 'typeorm';

@ObjectType()
@Entity()
export class ImageEntity {
  @PrimaryGeneratedColumn('uuid')
  @Field(() => String)
  id: string; 

  @Column({ default: false })
  @Field(() => Boolean, { defaultValue: false }) 
  isThumbnail: boolean; 
//isThumbnail?: boolean;  // it worked without question mark
}

//image.resolver.ts

import { Args, Mutation, Query, Resolver } from '@nestjs/graphql';
import { ImageEntity } from './entities/image.entity';
import { ImageService } from './image.service';

@Resolver()
export class ImageResolver {
  constructor(private readonly imageService: ImageService) {}

  @Mutation(() => ImageEntity)
  async createImage(
    @Args('imageUrl') imageUrl: string,
  //=============this part=================
    @Args('isThumbnail', { nullable: true }) isThumbnail?: boolean, // <--- that question mark I'm takin bout
    // @Args('isThumbnail', { nullable: true }) isThumbnail: boolean, // it work fine without the question mark
// what this thing for?  
  //========================================
  ) {
    return await this.imageService.create({ isThumbnail, imageUrl });
  }
}

Like on the code, it linked with TypeORM and GraphQL. And some of args (also related columns) are nullable.

I got it that {nullable : true} made both args and columns of GraphQL and TypeORM doable without the question mark. It worked fine, but on the nestjs doc, the question mark was right below the

@Field(()=>Some Type, {nullable: true}.

My question is that the question mark is just to indicate it is optional as typescript type?

ANSWER

Answered 2022-Feb-19 at 13:37

Yes, it means that it's optional, see https://www.geeksforgeeks.org/why-use-question-mark-in-typescript-variable/

It is understandable that it seems to be superfluous, the reason for this is that on the one hand, GraphQL has to know that it's nullable and on the other, Typescript forces you to define your types strongly.

GraphQL can be used by "normal" Javascript as well, which is very much loose-typed, in that use-case the only place where the optional nature of the item would be specified is the nullable attribute.

Source https://stackoverflow.com/questions/71185269

QUESTION

TypeORM composite foreign key

Asked 2022-Feb-14 at 20:14

In a first class, the primary key is composite:

@Entity({
  name: 'ClassA',
  database: Constants.DATABASE_NAME,
})
export class ClassA {
  @PrimaryColumn({
    name: 'Field1',
    type: 'varchar',
    length: 4,
  })
  field1: string;

  @PrimaryColumn({
    name: 'Field2',
    type: 'varchar',
    length: 2,
  })
  field2: string;

  @PrimaryColumn({
    name: 'Field3',
    type: 'integer',
  })
  field3: number;

  @OneToMany(() => ClassB, (classB) => classB.classA)
  classB: ClassB[];
}

In another class, the first class is used as a foreign key:

@Entity({
  name: 'ClassB',
  database: Constants.DATABASE_NAME,
})
export class ClassB {

  ...

  @ManyToOne(() => ClassA, (classA) => classA.classB, {
    cascade: true,
  })
  @JoinColumn([
    { name: 'Field1', referencedColumnName: 'field1' },
    { name: 'Field2', referencedColumnName: 'field2' },
    { name: 'Field3', referencedColumnName: 'field3' },
  ])
  classA: ClassA;
}

When I start NestJS using nest start, I get the error

code: "ER_FK_NO_INDEX_PARENT"
errno: 1822
sqlMessage: Failed to add the foreign key constraint. Missing index for constraint 'FK_1d19fe001872b5ee9ab545c18f8' in the referenced table 'ClassA'
sqlState: "HY000

I tried to alter the ClassA table and add indexes on each column of the primary key, and then an index of all columns of the primary key, but the error is still the same.

Is this possible to manage this case with TypeORM?

Relevant packages:

typeorm: 0.2.41
@nestjs/core: 8.0.0
@nestjs/typeorm: 8.0.3
mysql: 2.18.1

DB: MySQL v8.0 in a Docker container (mysql:latest)

Thank you.

Edit

It seems that the issue is that the table is created in more than one step with TypeORM. The table looks like this after the error message.

CREATE TABLE `ClassB` (
  `Date` datetime NOT NULL,
  `ClassAField1` varchar(4) NOT NULL,
  `ClassAField2` varchar(2) NOT NULL,
  `ClassAField3` int NOT NULL,
  PRIMARY KEY (`Date`,`ClassAField1`,`ClassAField2`,`ClassAField3`),
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

The error happens on the following query, where TypeORM tries to add the foreign key:

ALTER TABLE `ClassB`
ADD CONSTRAINT `FK_479eaf779e0d5f0d0a83bb9e30d`
FOREIGN KEY (`ClassAField1`, `ClassAField2`, `ClassAField3`)
REFERENCES `LandPlots`(`Field1`,`Field2`,`Field3`) ON DELETE NO ACTION ON UPDATE NO ACTION

I made a few tests, and the following query works as intended:

CREATE TABLE `ClassB` (
  `Date` datetime NOT NULL,
  `ClassAField1` varchar(4) NOT NULL,
  `ClassAField2` varchar(2) NOT NULL,
  `ClassAField3` int NOT NULL,
  PRIMARY KEY (`Date`),
  KEY `FK_e6b2926df2c758d8d8810e4345a` (`ClassAField1`, `ClassAField2`, `ClassAField3`),
  CONSTRAINT `FK_e6b2926df2c758d8d8810e4345a`
  FOREIGN KEY (`ClassAField1`, `ClassAField2`, `ClassAField3`)
  REFERENCES `ClassA` (`Field1`, `Field2`, `Field3`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

The difference seems to be the line KEY `FK_e6b2926df2c758d8d8810e4345a` (`ClassAField1`, `ClassAField2`, `ClassAField3`),, which is missing from the generated SQL by TypeORM.

From MySQL documentation, the KEY statement is synonymous to INDEX:

 KEY | INDEX

KEY is normally a synonym for INDEX. The key attribute PRIMARY KEY can also be specified as just KEY when given in a column definition. This was implemented for compatibility with other database systems.

So I tried to add the @Index decorator to the column but it did not change anything. I added logging of all executed queries, and it seems that the @Index decorator is not executed, so, maybe the @JoinColumn decorator has priority over it? (Tried to sort decorators different ways just in case).

The only solution that I can think of with TypeORM would be to generate a hash or concatenation of all 3 primary keys, and make it the sole primary key. Two drawbacks: Data duplication and CPU usage when parsing entities before insertion.

If someone has a better suggestion I would like to hear it.

Edit 2 following questions from @RickJames

Update statement:

UPDATE cb
SET cb.SomeField = 'NewValue'
FROM ClassB cb
JOIN ClassA ca
ON cb.Field1 = ca.Field1
AND cb.Field2 = ca.Field2
AND cb.Field3 = ca.Field3
WHERE ca.SomeOtherField LIKE '%partialvalue%'
AND cb.otherPK = 1

ANSWER

Answered 2022-Feb-14 at 20:14

That UPDATE might benefit from some of these indexes:

cb:  INDEX(otherPK, Field1, Field2, Field3)
ca:  INDEX(Field1, Field2, Field3, SomeOtherField)

Source https://stackoverflow.com/questions/70963321

QUESTION

TypeORM Inner Join Same Table

Asked 2022-Jan-14 at 20:39

I have a question I could not find an answer to online.

I have a single table and I am looking to remove duplicate entries:

My raw SQL query is:

#Perform delete duplicate logs with same order_id and message
DELETE t1 FROM order_logs t1
INNER  JOIN order_logs t2
WHERE t1.log_id < t2.log_id
AND t1.order_id = t2.order_id
AND t1.message = t2.message
AND t1.order_id = @ORDER_ID
AND t2.order_id = @ORDER_ID;

Here is my @Entity:

@Entity('customer_logs')
export class CustomerLog {
    @PrimaryGeneratedColumn()
    readonly log_id: number

    @Column()
    @ManyToOne(() => Customer, (customer) => customer.id, {
        onDelete: 'CASCADE',
    })
    @JoinColumn({ name: 'customer_id' })
    readonly customer_id: number

    @Column({ default: null, nullable: true })
    @ManyToOne(() => User, (user) => user.user_id)
    @JoinColumn({ name: 'user_id' })
    readonly user_id?: number

    @Column()
    @IsString()
    @MinLength(1)
    @MaxLength(255)
    readonly message: string

    @Column()
    @IsEnum(CustomerLogType)
    readonly type: CustomerLogType

    @Column({ type: 'json', default: null, nullable: true })
    @IsObject()
    readonly json?: object

    @CreateDateColumn()
    @Expose({ groups: ['ADMIN', 'OWNER'] })
    readonly created_at: Date

    @UpdateDateColumn()
    @Expose({ groups: ['ADMIN', 'OWNER'] })
    readonly updated_at: Date

    constructor(partial: Partial<CustomerLog>) {
        Object.assign(this, partial)
    }
}

Do you know how I would perform this query using TypeORM via the QueryBuilder?

ANSWER

Answered 2022-Jan-14 at 20:39

If you already have the raw SQL query right, you can just use that in code without the need of constructing it with QueryBuilder.

import { getConnection } from "typeorm";
.......{

await getConnection().query("DELETE t1 FROM order_logs t1
INNER  JOIN order_logs t2
WHERE t1.log_id < t2.log_id
AND t1.order_id = t2.order_id
AND t1.message = t2.message
AND t1.order_id = @ORDER_ID
AND t2.order_id = @ORDER_ID;"
    );

}

Source https://stackoverflow.com/questions/70604422

QUESTION

npm ERESOLVE unable to resolve dependency tree NestJs Passport

Asked 2022-Jan-12 at 22:05

I have following package.json

{
  "dependencies": {
    "@elastic/elasticsearch": "^7.16.0",
    "@nestjs/common": "^8.2.4",
    "@nestjs/config": "^1.1.5",
    "@nestjs/core": "^8.2.4",
    "@nestjs/jwt": "^8.0.0",
    "@nestjs/microservices": "^8.2.4",
    "@nestjs/passport": "^8.0.1",
    "@nestjs/platform-express": "^8.2.4",
    "@nestjs/testing": "^8.2.4",
    "@nestjs/websockets": "^8.2.4",
    "@nuxt/content": "^1.15.1",
    "@nuxt/typescript": "^2.8.1",
    "@nuxtjs/axios": "^5.13.6",
    "@nuxtjs/pwa": "^3.3.5",
    "@riophae/vue-treeselect": "0.4.0",
    "@typegoose/typegoose": "^9.4.0",
    "@types/fabric": "^4.5.6",
    "@types/multer": "^1.4.7",
    "acorn": "^8.6.0",
    "adm-zip": "^0.5.9",
    "ajv": "^8.8.2",
    "amqplib": "^0.8.0",
    "animejs": "^3.2.1",
    "axios": "^0.24.0",
    "bootstrap": "^5.1.3",
    "connect-mongo": "^4.6.0",
    "copyfiles": "^2.4.1",
    "core-js": "^3.20.1",
    "cross-env": "^7.0.3",
    "element-theme-dark": "^1.0.3",
    "element-ui": "^2.15.6",
    "express": "^4.17.2",
    "express-session": "^1.17.2",
    "fabric": "^4.6.0",
    "file-saver": "^2.0.5",
    "glob": "^7.2.0",
    "http-status-codes": "^2.1.4",
    "jQuery-QueryBuilder": "^2.6.2",
    "jquery": "^3.6.0",
    "jquery-ui-dist": "^1.13.0",
    "material-icons": "^1.10.4",
    "mongodb": "^4.2.2",
    "mongoose": "^6.1.3",
    "multer": "^1.4.4",
    "node-cron": "^3.0.0",
    "nprogress": "^0.2.0",
    "nuxt": "^2.15.8",
    "nuxt-class-component": "^1.3.0",
    "oidc-client": "^1.11.5",
    "openid-client": "^5.1.1",
    "passport": "^0.5.2",
    "passport-jwt": "^4.0.0",
    "passport-local": "^1.0.0",
    "popper.js": "^1.16.1",
    "redis": "^4.0.1",
    "reflect-metadata": "^0.1.13",
    "regenerator-runtime": "^0.13.9",
    "register-service-worker": "^1.7.2",
    "rimraf": "^3.0.2",
    "rxjs": "^7.4.0",
    "splitpanes": "^2.3.8",
    "ts-loader": "^9.2.6",
    "typegoose": "^5.9.1",
    "typeorm": "^0.2.41",
    "typescript": "^4.5.4",
    "vue": "^2.6.14",
    "vue-class-component": "^7.2.6",
    "vue-context": "^6.0.0",
    "vue-drag-drop": "^1.1.4",
    "vue-grid-layout": "^2.3.12",
    "vue-property-decorator": "^9.1.2",
    "vue-quill-editor": "^3.0.6",
    "vue-router": "^3.5.3",
    "vue-runtime-helpers": "^1.1.2",
    "vue-server-renderer": "^2.6.14",
    "vue-simple-uploader": "^0.7.6",
    "vuetify": "^2.6.1",
    "vuetify-loader": "^1.7.3",
    "vuex-class": "^0.3.2",
    "vuex-class-component": "^2.3.6",
    "webpack-node-externals": "^3.0.0",
    "winston": "^3.3.3"
  },
  "devDependencies": {
    "@babel/plugin-transform-modules-commonjs": "^7.16.5",
    "@nuxt/config": "^2.15.8",
    "@nuxt/types": "^2.15.8",
    "@nuxt/typescript-build": "^2.1.0",
    "@nuxtjs/stylelint-module": "^4.1.0",
    "@types/adm-zip": "^0.4.34",
    "@types/amqplib": "^0.8.2",
    "@types/animejs": "^3.1.4",
    "@types/chai": "^4.3.0",
    "@types/file-saver": "^2.0.4",
    "@types/jest": "^27.0.3",
    "@types/jquery": "^3.5.11",
    "@types/jqueryui": "^1.12.16",
    "@types/mocha": "^9.0.0",
    "@types/mongodb": "^4.0.6",
    "@types/node": "^17.0.4",
    "@types/nprogress": "0.2.0",
    "@types/quill": "^2.0.9",
    "@types/redis": "^4.0.10",
    "@types/splitpanes": "^2.2.1",
    "@types/webpack-env": "^1.16.3",
    "@typescript-eslint/eslint-plugin": "^5.8.0",
    "@typescript-eslint/eslint-plugin-tslint": "^5.8.0",
    "@typescript-eslint/parser": "^5.8.0",
    "@vue/cli-plugin-babel": "^4.5.15",
    "@vue/cli-plugin-e2e-cypress": "^4.5.15",
    "@vue/cli-plugin-pwa": "^4.5.15",
    "@vue/cli-plugin-typescript": "^4.5.15",
    "@vue/cli-plugin-unit-mocha": "^4.5.15",
    "@vue/cli-service": "^4.5.15",
    "@vue/test-utils": "^1.3.0",
    "babel-plugin-component": "^1.1.1",
    "babel-plugin-transform-class-properties": "^6.24.1",
    "babel-plugin-transform-decorators-legacy": "^1.3.5",
    "chai": "^4.3.4",
    "eslint": "^8.5.0",
    "eslint-config-prettier": "^8.3.0",
    "eslint-plugin-import": "^2.25.3",
    "eslint-plugin-jsdoc": "^37.4.0",
    "eslint-plugin-no-null": "^1.0.2",
    "eslint-plugin-prefer-arrow": "^1.2.3",
    "eslint-plugin-unicorn": "^39.0.0",
    "jest": "^27.4.5",
    "lint-staged": "^12.1.4",
    "node-sass": "^7.0.0",
    "nodemon": "^2.0.15",
    "nuxt-property-decorator": "^2.9.1",
    "nuxt-ts": "^2.8.1",
    "prettier": "^2.5.1",
    "sass-loader": "^12.4.0",
    "stylus": "^0.56.0",
    "stylus-loader": "^6.2.0",
    "ts-node": "^10.4.0",
    "tsconfig-paths": "^3.12.0",
    "tslint": "^5.20.1",
    "tslint-config-prettier": "^1.18.0",
    "tslint-plugin-prettier": "^2.3.0",
    "vue-template-compiler": "^2.6.14",
    "webpack": "^5.65.0",
    "webpack-cli": "^4.9.1",
    "webpack-shell-plugin": "^0.5.0"
  }
}

when I try to install above dependencies I am getting following error.

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: ecdisco@1.0.0
npm ERR! Found: passport@0.5.2
npm ERR! node_modules/passport
npm ERR!   passport@"^0.5.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer passport@"^0.4.0" from @nestjs/passport@8.0.1
npm ERR! node_modules/@nestjs/passport
npm ERR!   @nestjs/passport@"^8.0.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\user\AppData\Local\npm-cache\eresolve-report.txt for a full report.

My Node version is: v16.13.0 My npm version is: 8.1.0

I don't want to use incorrect dependency by using --force and --legacy-peer-deps options. What solution do I have?

ANSWER

Answered 2021-Dec-28 at 13:15

To resolve this issue update the "passport" lib version in your package.json: from "passport": "^0.5.2", to "passport": "^0.4.0", so it's same as used in @nestjs/passport@8.0.1.

Source https://stackoverflow.com/questions/70479557

QUESTION

Docker NodeJS app cant connect to postgres database

Asked 2022-Jan-11 at 12:40

I am farely new to docker and docker-compose. I tried to spin up a few services using docker which contain of a nodejs (Nest.js) api, a postgres db and pgadmin. Without the API (nodejs) app beeing dockerized I could connect to the docker database containers, but now that I also have dockerized the node app, it is not connecting anymore and I am clueless why. Is there anything wrong with the way I have set it up?

Here is my docker-compose file

version: "3"
services:
  nftapi:
    env_file:
      - .env
    build:
      context: .
    ports:
      - '5000:5000'
    depends_on: 
      - postgres
    volumes: 
      - .:/app
      - /app/node_modules
    networks:
      - postgres
      
  postgres:
    container_name: postgres
    image: postgres:latest
    ports:
    - "5432:5432"
    volumes:
    - /data/postgres:/data/postgres
    env_file:
    - docker.env
    networks:
    - postgres
 
  pgadmin:
    links:
    - postgres:postgres
    container_name: pgadmin
    image: dpage/pgadmin4
    ports:
    - "8080:80"
    volumes:
    - /data/pgadmin:/root/.pgadmin
    env_file:
    - docker.env
    networks:
    - postgres
 
networks:
  postgres:
    driver: bridge

This is the nodejs app Dockerfile which builds successfully and in the logs I see the app is trying to connect to the databse but it cant (no specific error) just that it doesnt find the db.

# Image source
FROM node:14-alpine

# Docker working directory
WORKDIR /app

# Copying file into APP directory of docker
COPY ./package.json /app/

RUN apk update && \
    apk add git
# Then install the NPM module
RUN yarn install

# Copy current directory to APP folder
COPY . /app/

EXPOSE 5000
CMD ["npm", "run", "start:dev"]

I have 2 env files in my projecs root directory.

.env
docker.env

As mentioned above, when I remove the "nftapi" service from docker and run the nodejs up with a simple npm start it is connecting to the postgres container.

TypeOrmModule.forRoot({
      type: 'postgres',
      host: process.env.POSTGRES_HOST,
      port: Number(process.env.POSTGRES_PORT),
      username: process.env.POSTGRES_USER,
      password: process.env.POSTGRES_PASSWORD,
      database: process.env.POSTGRES_DB,
      synchronize:true,
      entities: ['dist/**/*.entity{.ts,.js}'],
    }),

The host from the .env file that is used in the typeorm module is localhost

ANSWER

Answered 2022-Jan-11 at 12:40

When using networks with docker-compose you should use the name of the service as you hostname.

so in your case the hostname should be postgres and not localhost

You can read more about at here: https://docs.docker.com/compose/networking/

Source https://stackoverflow.com/questions/70665871

QUESTION

Mock bcrypt module module in Nest.js

Asked 2022-Jan-08 at 19:18

I'm trying to mock bcrypt hash method implementation, but get following error:

Error: thrown: "Exceeded timeout of 5000 ms for a test.
Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

I've tried to increase timeout up to 30000. Also I've tried to mock entire bcrypt module like jest.mock('bcrypt'). I'm new to testing and there are may be some logical errors or bad practises. I will be grateful if you point to them.

My code:

import { UserService } from '../user.service';
import { Test, TestingModule } from '@nestjs/testing';
import { Repository } from 'typeorm';
import { getRepositoryToken } from '@nestjs/typeorm';
import * as bcrypt from 'bcrypt';

import { UserEntity } from '../user.entity';
import { UserRepository } from '../user.repository';
import { CreateUserDto } from '../dto/create-user.dto';
import { userStub } from './stubs/user.stub';

describe('UserService', () => {
  let userService: UserService;
  let userRepository: Repository<UserEntity>;

  beforeAll(async () => {
    const module: TestingModule = await Test.createTestingModule({
      providers: [
        UserService,
        {
          provide: getRepositoryToken(UserRepository),
          useClass: Repository,
        },
      ],
    }).compile();

    userService = module.get<UserService>(UserService);
    userRepository = module.get<Repository<UserEntity>>(
      getRepositoryToken(UserRepository),
    );
  });

  it('should define UserService', () => {
    expect(userService).toBeDefined();
  });

  it('should define userRepository', () => {
    expect(userRepository).toBeDefined();
  });

  describe('createUser method', () => {
    it('has called with valid data', async () => {
      const createUserDto: CreateUserDto = {
        email: userStub().email,
        firstName: userStub().firstName,
        lastName: userStub().lastName,
        password: userStub().password,
      };
      const user: UserEntity = userStub();
      const spiedBcryptHashMethod = jest
        .spyOn(bcrypt, 'hash')
        .mockImplementation(() => Promise.resolve(''));
      const spiedRepositoryCreateMethod = jest
        .spyOn(userRepository, 'create')
        .mockReturnValue(user);
      const spiedRepositorySaveMethod = jest
        .spyOn(userRepository, 'save')
        .mockResolvedValue(user);

      const createUserResult = await userService.createUser(createUserDto);

      expect(spiedBcryptHashMethod).toHaveBeenCalled();
      expect(spiedRepositoryCreateMethod).toHaveBeenCalled();
      expect(spiedRepositorySaveMethod).toHaveBeenCalledWith(user);
      expect(createUserResult).toEqual(user);
    });
  });
});

Error is appeared here:

const spiedBcryptHashMethod = jest
        .spyOn(bcrypt, 'hash')
        .mockImplementation(() => Promise.resolve(''));

My userService code:

import { Injectable } from '@nestjs/common';
import { InjectRepository } from '@nestjs/typeorm';
import * as bcrypt from 'bcrypt';

import { UserRepository } from './user.repository';
import { CreateUserDto } from './dto/create-user.dto';
import { UserEntity } from './user.entity';

@Injectable()
export class UserService {
  constructor(
    @InjectRepository(UserRepository) private userRepository: UserRepository,
  ) {}

  public async createUser(createUserDto: CreateUserDto): Promise<UserEntity> {
    return await this.userRepository.save(
      this.userRepository.create({
        ...createUserDto,
        password: await new Promise((resolve, reject) => {
          bcrypt.hash(createUserDto.password, 10, (err, encrypted) => {
            if (err) {
              reject(err);
            }

            resolve(encrypted);
          });
        }).then((onFilled: string) => onFilled),
      }),
    );
  }
}

ANSWER

Answered 2022-Jan-08 at 19:18

Okay, so there's a lot to say about your service code...

The immediate issue you're having the problem is because you're mocking bcrypt's hash method to return a promise, but using the method as it returns a callback. IF you want to keep using the callback mixed with promises approach, you'd need to do something like

jest.spyOn(bcrypt, 'hash').mockImplementation((pass, salt, cb) => cb(null, ''))

This will be essentially the same as the Promise.resolve('').

HOWEVER I do not suggest this. Bcrypt has built in promise support, so instead of wrapping the callback with your own promise, you can just do await bcrypt.hash(pass, salt) and you'll get the hashed password back, then your Promise.resolve('') will work as you intend it too. I don't see the need for the then((onFullfilled: string) => onFullfilled) either, but that would go away if you remove the custom promise anyways.

Generally, try to stick with a single asynchronous approach. All callbacks (not suggested anymore), all promises (better), or all async/await (pretty much the standard now).

Source https://stackoverflow.com/questions/70634909

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install typeorm

Install the npm package:.
Install the npm package: npm install typeorm --save
You need to install reflect-metadata shim: npm install reflect-metadata --save and import it somewhere in the global place of your app (for example in app.ts): import "reflect-metadata";
You may need to install node typings: npm install @types/node --save-dev
Install a database driver: for MySQL or MariaDB npm install mysql --save (you can install mysql2 instead as well) for PostgreSQL or CockroachDB npm install pg --save for SQLite npm install sqlite3 --save for Microsoft SQL Server npm install mssql --save for sql.js npm install sql.js --save for Oracle npm install oracledb --save To make the Oracle driver work, you need to follow the installation instructions from their site. for SAP Hana npm i @sap/hana-client npm i hdb-pool SAP Hana support made possible by the sponsorship of Neptune Software. for MongoDB (experimental) npm install mongodb@^3.6.0 --save for NativeScript, react-native and Cordova Check documentation of supported platforms Install only one of them, depending on which database you use.
The quickest way to get started with TypeORM is to use its CLI commands to generate a starter project. Quick start works only if you are using TypeORM in a NodeJS application. If you are using other platforms, proceed to the step-by-step guide.

Support

Learn about contribution here and how to setup your development environment here.

Find more information at:

Reuse Trending Solutions

14 best Python Telegram Bot

21 best C# Game Development in 2023

Image Resizing using OpenCV in Python

How to Validate an Email Address in JavaScript

Age Calculator using JavaScript

28 best Python Face Recognition in 2023

Display Stopwatch in ReactJs

Google Maps Integration with Location

Disease Predictor

Resolving Gender Bias in AI

Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
over 650 million Knowledge Items

Find more libraries

Reuse Solution Kits and Libraries Curated by Popular Use Cases

Save this library and start creating your kit

Clone

HTTPS

https://github.com/typeorm/typeorm.git

CLI

gh repo clone typeorm/typeorm

SSH

git@github.com:typeorm/typeorm.git

Download

Share this Page

See Similar Libraries in

Object-Relational Mapping

Reuse Utilities Kits

Open Source Intelligence

Ai Hulks App Kit

16 best Python Animation Libraries in 2023

11 best Python Regex libraries in 2023

See all related Kits

Consider Popular Object-Relational Mapping Libraries

by django

by typeorm

by go-gorm

spring-boot-demo

by xkcoding

by mybatis

See all Object-Relational Mapping Libraries

Try Top Libraries by typeorm

typescript-express-example

by typeorm TypeScript

typeorm-typedi-extensions

by typeorm TypeScript

typescript-koa-example

by typeorm TypeScript

typescript-example

by typeorm TypeScript

typeorm-routing-controllers-extensions

by typeorm TypeScript

See all Libraries by this author

Compare Object-Relational Mapping Libraries with Highest Support

by django

by mybatis

by querydsl

by doctrine

spring-data-jpa

by spring-projects

See all Object-Relational Mapping Libraries

Compare Object-Relational Mapping Libraries with Highest Quality

spring-data-demos

by gordonad

by cr2121

by Fruzenshtein

dropwizard-spring

by nhuray

by seijoed

See all Object-Relational Mapping Libraries

Compare Object-Relational Mapping Libraries with Highest Security

swing-spring-jpa-crud

by yaw

javafx-jpa-crud

by yaw

spring-data-demos

by gordonad

by cr2121

by Fruzenshtein

See all Object-Relational Mapping Libraries

Compare Object-Relational Mapping Libraries with Permissive License

by j256

by grossopa

musicbrainz-data

by lastfm

by brettwooldridge

jpa-query-by-example

by jaxio

See all Object-Relational Mapping Libraries

Compare Object-Relational Mapping Libraries with Highest Reuse

phoenix-hibernate-dialect

by jruesga

by streamx-co

spring-hibernate-query-utils

by yannbriancon

by DISID

holon-datastore-jdbc

by holon-platform

See all Object-Relational Mapping Libraries

Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
over 650 million Knowledge Items

Find more libraries

Reuse Solution Kits and Libraries Curated by Popular Use Cases

Save this library and start creating your kit

Open Weaver – Develop Applications Faster with Open Source

kandi

Develop Custom Functions

Develop Projects with Kits

Explore Popular Libraries

Product Tour

Community and Support

Self Paced Certifications

Hackathons and Events

FutureSkills Prime

Company

Follow

Terms
Privacy policy
© 2023 Open Weaver Inc.

© 2023 Open Weaver Inc.