Skip to content

Definitive FAQ entry on node_modules limitation #40

@robpalme

Description

@robpalme

We've seen folk ask the same question multiple times on why the "no transform of .ts files inside node_modules" restriction exists.

To avoid going over well-trodden ground, we should have a definitive URL we can offer to folk who might ask this question in future. This probably should be an FAQ entry, but equally could be a dedicated doc page. The content should ideally leave the reader thinking "wow - the basis of that decision is clearly communicated" even if the reader disagrees with the conclusion.

There were multiple reasons for the restriction. The article should declaratively list the full set of concerns followed by a summary rationale for the current decision. Ideally each concern should have a snappy title and/or sub-URL to allow ease-of-referencing in future conversations.

Anyone could take on this issue by poring over the historical conversations in Github issues and then summarising. Ideally it would be written by a TypeScript representative given they shared the strongest concerns. At the very least it must be reviewed by TS folk before landing.

Note: The issue is purely to describe past decisions - not to change anything. Replies campaigning for change should be considered off-topic.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions