Skip to content

Conversation

weswigham
Copy link
Member

This way we can use string types more quickly. After this is merged, make sure you (as an individual) jake clean and npm install.

@weswigham
Copy link
Member Author

Curiously, this is one of those odd situations where the differences between npm@2 and npm@3 cause compilation failures. Since tslint depends on TS, with npm@3 we have a top-level "typescript" to require which is shared with tslint. To get the same behavior with npm@2 we need to add typescript@next as a devDependency so it gets installed at the top level by npm@2. Ideally, we'd like to somehow replace that dependency with the LKG version - I think that should be possible with a npm-shrinkwrap.json, but I'm not sure how important that is.

@DanielRosenwasser
Copy link
Member

Sure why not 👍

weswigham added a commit that referenced this pull request Nov 14, 2015
@weswigham weswigham merged commit 117da7f into microsoft:master Nov 14, 2015
@weswigham weswigham deleted the tslint@next branch August 17, 2017 23:04
@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