Skip to content

treat failures to resolve module name as missing packages #12237

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
merged 1 commit into from
Nov 14, 2016

Conversation

vladima
Copy link
Contributor

@vladima vladima commented Nov 14, 2016

// CC @mhegazy, @billti

@vladima vladima merged commit 0a3afb5 into release-2.0.5 Nov 14, 2016
@vladima vladima deleted the vladima/guard-module-resolution branch November 14, 2016 22:57
@mhegazy
Copy link
Contributor

mhegazy commented Nov 15, 2016

can we add another check to filterTypings to check this.packageNameToTypingLocation[packageName]

@mhegazy
Copy link
Contributor

mhegazy commented Nov 15, 2016

and in master as well.

vladima added a commit that referenced this pull request Nov 15, 2016
* treat failures to resolve module name as missing packages (#12237)

* added extra check to prevent multiple installation of the same typing, added version field to telemetry event (#12258)

* added extra check to prevent multiple installation of the same typing, added version field to telemetry event

* use ts.version

* switch to execSync to ensure that no install orders are interleaved (#12259)

* Make sure version is public

* Update file with version string for nightly release
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
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.

3 participants