Skip to content
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

Windows newline issue #5

Closed
joelhegg opened this issue Aug 15, 2017 · 11 comments
Closed

Windows newline issue #5

joelhegg opened this issue Aug 15, 2017 · 11 comments

Comments

@joelhegg
Copy link

joelhegg commented Aug 15, 2017

I'm trying to use this module, but it's giving the error described here: ifrost/afterwriting-labs#69

My temporary work around is to run

dos2unix node_modules/tsc-watch/tsc-watch.js

As a permanent fix can you republish with core.autocrlf = false as described above?

@alexkatz
Copy link

I'm running macOS and ran into this issue as well (env: node\r: No such file or directory). I dug around online and found the solution of opening up tsc-watch.js with vim and running :set ff=unix to transform the line endings. Was a quick fix for macOS. Not sure if it interferes with Windows.

@OrKoN
Copy link

OrKoN commented Aug 23, 2017

I have the same problem as @alexkatz with the latest version

@mpicard
Copy link

mpicard commented Sep 20, 2017

This is so simple, can you please publish the fix soon?

@obedm503
Copy link

having the same issue. my current solution is to run it from my package.json scripts as npx tsc-watch

@bjornstar
Copy link

I ran into this problem when I install it with yarn, but it works perfectly fine when I install it with npm.

I've published @sensu/tsc-watch with the newlines fixed.

@gilamran
Copy link
Owner

gilamran commented Dec 5, 2017

Fixed on version 1.0.10

@gilamran gilamran closed this as completed Dec 5, 2017
@nathanmsmith
Copy link

Has this popped back up for anyone? I'm getting the same error on 1.0.13.

@gilamran
Copy link
Owner

@nathunsmitty I'm not working with a Mac so I have hard time fixing this... if anyone else is getting this error, please re-open this issue.

@mikestead
Copy link

mikestead commented Jan 3, 2018

@gilamran I can confirm this has been reintroduced (on mac). If I drop back to v1.0.10 things work well. Not sure which commit caused the regression.

I'd re-open but don't have permissions.

@gilamran
Copy link
Owner

gilamran commented Jan 3, 2018

@bjornstar, can you help with this issue? maybe a PR?

@gilamran gilamran reopened this Jan 3, 2018
@gilamran
Copy link
Owner

Fixed on v1.0.14

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

No branches or pull requests

9 participants