Skip to content

Treat explicit imports from node_modules as external library imports #16364

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

Merged
4 commits merged into from
Aug 17, 2017

Conversation

ghost
Copy link

@ghost ghost commented Jun 8, 2017

Fixes #15970 and #15755

@@ -3857,12 +3857,7 @@ namespace ts {
export interface ResolvedModule {
/** Path of the file the module was resolved to. */
resolvedFileName: string;
/**
Copy link
Author

@ghost ghost Jun 8, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment didn't describe what we're actually doing. We don't validate the contents of files in any way while doing module resolution.

@ghost ghost requested a review from aozgaa July 10, 2017 19:50
@aozgaa
Copy link
Contributor

aozgaa commented Aug 15, 2017

I'm not sure what the ramifications of turning everything in node_modules into external library imports is (aside from avoiding the inadvertent compilation of *.js files in the linked issues).

Specifically, what changes in our treatment of a module when it is an external library import vs. an import within the project?

@aozgaa
Copy link
Contributor

aozgaa commented Aug 17, 2017

Talked offline, LGTM

@ghost ghost merged commit eef7d8b into master Aug 17, 2017
@ghost ghost deleted the explicit-node_modules branch August 17, 2017 20:26
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants