Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Large typings file (xxx.d.ts) problems when using WebStorm #9000

Closed
chutch1122 opened this issue Feb 15, 2022 · 4 comments
Closed

Large typings file (xxx.d.ts) problems when using WebStorm #9000

chutch1122 opened this issue Feb 15, 2022 · 4 comments
Labels
impact/usability Something that impacts users' ability to use the product easily and intuitively kind/enhancement Improvements or new features resolution/duplicate This issue is a duplicate of another issue

Comments

@chutch1122
Copy link

When using WebStorm with the TypeScript/Node module, it seems like having the .d.ts typings file as large as it is (in the case of types/inputs.d.ts with @pulumi/azure-native@1.58.0 it is ~25 MB) is causing the type completion and auto-import features to not work. These features work with most other .d.ts typings files (eg: documentdb/mongoDBResourceMongoDBCollection.d.ts - which happens to be pretty small).

I suspect that if types/inputs.d.ts could be split apart into multiple .d.ts files then type completion and auto-import would work properly.

Large file "Read Only Mode"- types/inputs.d.ts
image

Small file - documentdb/mongoDBResourceMongoDBCollection.d.ts
image

@danielrbradley danielrbradley added impact/usability Something that impacts users' ability to use the product easily and intuitively kind/enhancement Improvements or new features labels Feb 16, 2022
@danielrbradley
Copy link
Member

danielrbradley commented Feb 16, 2022

Does webstorm have the same issue if you only import the specific input/output types namespace? e.g.

import { aad, documentdb } from "@pulumi/azure-native/types/input";

@chutch1122
Copy link
Author

Yeah, it does unfortunately.

inputs issue

@danielrbradley danielrbradley transferred this issue from pulumi/pulumi-azure-native Feb 16, 2022
@danielrbradley
Copy link
Member

@pulumi/platform-core transfering this as it would appear this could only be solved by changing the way we generate the files for input and output types. Ideally, we'd split each namespace's types into separate files so they could be referenced individually to solve performances issues such as this one.

@danielrbradley danielrbradley added the needs-triage Needs attention from the triage team label Feb 16, 2022
@mikhailshilkov
Copy link
Member

Tracked in #6571

@mikhailshilkov mikhailshilkov added resolution/duplicate This issue is a duplicate of another issue and removed needs-triage Needs attention from the triage team labels Feb 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/usability Something that impacts users' ability to use the product easily and intuitively kind/enhancement Improvements or new features resolution/duplicate This issue is a duplicate of another issue
Projects
None yet
Development

No branches or pull requests

3 participants