atom-typescript encounters difficulty locating typings

Question

atom-typescript encounters difficulty locating typings

After setting up a new Angular/Typescript project in Atom with atom-typescript, I encountered an issue. The main angular module file imports all modules and type definition files, but errors are now showing in my .ts files. This is due to atom-typescript not recognizing the typings.

For example:

Module 'ng' has no exported member 'IScope' at line 1 col 32

To resolve this, I could individually add reference paths to each ts file like

/// <reference path="../../.tmp/typings/tsd.d.ts" />

, but that seems inefficient.

Since the errors are from atom-typescript, is there a way to specify the location of type defintion files in the project settings? Any other suggestions on how to address this?

typescript atom-editor

Answer 1

Answer №1

Insert the necessary typings into the tsconfig.json file along with the rest of the TypeScript files in the files section.

If you're using atom-typescript, you can also utilize glob patterns, like so:

{
...
    "filesGlob": [
        "./typescript/**/*.ts",
        "./typescript/**/*.tsx",
        "./typings/**/*.d.ts"
    ]
...
}

The files section will update automatically.

Edit

Since this feature is officially supported by Typescript now, a more universal solution (compatible across different IDEs) might involve utilizing the exclude property in the tsconfig file.

This approach operates in the opposite manner: compile everything except for what is specified in the exclusions (usually content within node_modules and static assets such as those in public)

{
    "compilerOptions": {
        ...
    },
    "exclude": [
        "node_modules",
        "public"
    ]
}

For official information, visit this link

Answer 2

Insert the necessary typings into the tsconfig.json file along with the rest of the TypeScript files in the files section.

If you're using atom-typescript, you can also utilize glob patterns, like so:

{
...
    "filesGlob": [
        "./typescript/**/*.ts",
        "./typescript/**/*.tsx",
        "./typings/**/*.d.ts"
    ]
...
}

The files section will update automatically.

Edit

Since this feature is officially supported by Typescript now, a more universal solution (compatible across different IDEs) might involve utilizing the exclude property in the tsconfig file.

This approach operates in the opposite manner: compile everything except for what is specified in the exclusions (usually content within node_modules and static assets such as those in public)

{
    "compilerOptions": {
        ...
    },
    "exclude": [
        "node_modules",
        "public"
    ]
}

For official information, visit this link

atom-typescript encounters difficulty locating typings

Answer №1

Similar questions

A guide on including a class to a DOM element in Angular 6 without relying on Jquery

What is the best way to incorporate node_module during the iOS build process in Ionic 2?

In TypeScript, values other than numbers or strings can be accepted as parameters, even when the expected type is a

Material UI offers a feature that allows for the grouping and auto-completion sorting

Ways to grant access beyond the local host

Sharing a variable between an Angular component and a service

Error: Component with nested FormGroup does not have a valid value accessor for form control in Angular

Can someone explain how this "const s: string = ['a'][1];" is considered a valid Typescript expression?

Managing Angular routing: selectively updating named outlets without reloading submodules

Explain to me the process of passing functions in TypeScript

Launching React Native in Visual Studio Code: launchReactNative.js

Using Karma-Jasmine to Import Spy without anyImplicitAny

Error encountered when using a connected component in Typescript with Redux

leveraging two connected hooks

Collective picture in the exhibit

Differences between ts-loader and babel-loader when working with TypeScript in webpack

arrange items based on their category into arrays

Updating Dropdown Selection in Angular 9 and 10

What is the process for deploying a Lambda function using Terraform that has been generated with CDKTF

Troubleshooting Next.js 14 JWT Session Error in Conjunction with Next Auth - addressing a type