Skip to content

Fix ts-node running on composite projects #657

New issue

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

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

Already on GitHub? # to your account

Merged
merged 1 commit into from
Aug 7, 2018
Merged

Fix ts-node running on composite projects #657

merged 1 commit into from
Aug 7, 2018

Conversation

sgoll
Copy link
Contributor

@sgoll sgoll commented Aug 6, 2018

See #656 for details.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 85.101% when pulling a6a3020 on sgoll:master into 2017b3a on TypeStrong:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 85.101% when pulling a6a3020 on sgoll:master into 2017b3a on TypeStrong:master.

@blakeembrey blakeembrey merged commit 6df09a9 into TypeStrong:master Aug 7, 2018
@blakeembrey
Copy link
Member

Thanks! 👍

@dotbear
Copy link

dotbear commented Aug 9, 2018

Any chance of this getting released anytime soon? :)

@sgoll
Copy link
Contributor Author

sgoll commented Aug 10, 2018

I'd also like a quick patch release for this since it's somewhat disruptive to my workflow and patching ts-node inline after every npm/yarn install is only fun for so long before it becomes tedious. :)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants