What is the process of importing types in TypeScript?

Question

What is the process of importing types in TypeScript?

Here is the export I am working with:

import * as jwt from 'jsonwebtoken';
  ...
export type MyJsonWebToken = typeof jwt;

Next, when attempting to use it in my code:

export class AuthService {
  constructor(
    @Inject(constants.JWT) private readonly jsonWebToken: MyJsonWebToken,
    //                                                  issue here ^  

  ){}

An error is being generated, specifically related to MyJsonWebToken:

ReferenceError: jwt_provider_1 is not defined
    at Object.<anonymous> (D:\Learning\nest\project\server\modules\Auth\auth.service.ts:9:59)
    at Module._compile (module.js:573:30)
    at Module.m._compile (D:\Learning\nest\project\node_modules\ts-node\src\index.ts:392:23)
    at Module._extensions..js (module.js:584:10)
    at Object.require.extensions.(anonymous function) [as .ts] (D:\Learning\nest\project\node_modules\ts-node\src\index.ts:395:12)
    at Module.load (module.js:507:32)
    at tryModuleLoad (module.js:470:12)
    at Function.Module._load (module.js:462:3)
    at Module.require (module.js:517:17)
    at require (internal/module.js:11:18)

typescript nestjs

Answer 1

Answer №1

It is important to note that Nest's dependency injection system may not seamlessly integrate with certain non-DI libraries, like JWT. The recommended approach is to create a wrapper component that follows the documentation of the JWT library. Subsequently, you can inject this wrapper into your controllers as needed.

@Component()
export class CustomJWT {
    generateToken(data) {
        jwt.sign() // implementation
    }

    validateToken() {
        jwt.verify() // implementation
    }
}

Answer 2

It is important to note that Nest's dependency injection system may not seamlessly integrate with certain non-DI libraries, like JWT. The recommended approach is to create a wrapper component that follows the documentation of the JWT library. Subsequently, you can inject this wrapper into your controllers as needed.

@Component()
export class CustomJWT {
    generateToken(data) {
        jwt.sign() // implementation
    }

    validateToken() {
        jwt.verify() // implementation
    }
}

Answer 3

Answer №2

It appears that NestJS has an issue with the * as foo style import statements. In my monorepo, I have custom paths set up in my tsconfig.json and attempted this approach:

import * as sharedApi from '@shared-interfaces/api';
//use `sharedApi.IWhatever` somewhere below

However, this resulted in an error. Making a slight adjustment to the import style made it function correctly:

import { IWhatever } from '@shared-interfaces/api';
//use `IWhatever` somewhere below

NestJS can be quite peculiar at times. It offers many great features along with some quirks.

Answer 4

It appears that NestJS has an issue with the * as foo style import statements. In my monorepo, I have custom paths set up in my tsconfig.json and attempted this approach:

import * as sharedApi from '@shared-interfaces/api';
//use `sharedApi.IWhatever` somewhere below

However, this resulted in an error. Making a slight adjustment to the import style made it function correctly:

import { IWhatever } from '@shared-interfaces/api';
//use `IWhatever` somewhere below

NestJS can be quite peculiar at times. It offers many great features along with some quirks.

Answer 5

Answer №3

After doing some research, I came up with the following solution:

import * as types from '...';
// You can then utilize it in this way:
jsonWebToken: types.JsonWebToken,

However, I find this solution to be quite ineffective and it's really disheartening. Could this possibly be an issue with TypeScript?

Answer 6

After doing some research, I came up with the following solution:

import * as types from '...';
// You can then utilize it in this way:
jsonWebToken: types.JsonWebToken,

However, I find this solution to be quite ineffective and it's really disheartening. Could this possibly be an issue with TypeScript?

What is the process of importing types in TypeScript?

Answer №1

Answer №2

Answer №3

Similar questions

Is there a way for me to properly type the OAuthClient coming from googleapis?

Tips for utilizing the JS attribute "offsetWidth" within Angular 4

Troubleshooting problems encountered when duplicating an array in JavaScript

The step-by-step guide to fixing a Gigwage client eslint error using nestJS

Is it feasible to connect to an output component without using EventEmitter?

Issue with selecting a value in React MUI and default value not being defined

Navigating to view component in Angular2 Routing: Issue with router-link click event not working

Is there a better approach to verifying an error code in a `Response` body without relying on `clone()` in a Cloudflare proxy worker?

What is the best way to ensure that Interface (or type) Properties always begin with a particular character?

Exploring the possibilities of integrating jQuery into Angular 2 using Javascript

The parameter type ‘DocumentData’ cannot be assigned to type ‘never’ in this argument

Issue with npm resolution due to package requiring another third-party dependency

The attribute is not found on the combined type

Ionic: Fixed button located at the bottom of a specific ion-slide

The promise callback in Angular2 is unable to access this

Ways to customize the OverridableComponent interface within Material-UI

Getting started with TypeScript in combination with Node.js, Express, and MongoDB

Nextjs 14 experiences full page loading due to the presence of multiple root layouts

How can we ensure a generic async function with a return type that is also generic in Typescript?

There is a delay in updating ng-if/ng-hide in real time on the HTML page