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

Issues running on macOS due to line endings #6

Open
Dids opened this issue Oct 27, 2017 · 7 comments
Open

Issues running on macOS due to line endings #6

Dids opened this issue Oct 27, 2017 · 7 comments
Assignees
Labels

Comments

@Dids
Copy link

Dids commented Oct 27, 2017

Running muddler produces this error:

env: node\r: No such file or directory

This is due to /usr/local/bin/muddle (or muddle.js) having line endings in the DOS format. A similar issue can be seen here.

The fix is to simply convert the line endings from DOS to unix, at which point it should be compatible across all platforms.

A long term solution to this might be a simple as adding a .gitattributes file that does the formatting on it's own, as seen here.

@Dids
Copy link
Author

Dids commented Oct 27, 2017

I can also confirm that this works as a temporary workaround:

sudo vim /usr/local/bin/muddle
:set ff=unix
:x

@jcjolley
Copy link
Owner

Thanks for the bug report @Dids! If it's urgent I'll happily merge a pull request. If not, I should be able to handle it this evening.

@jcjolley
Copy link
Owner

I took a minute during lunch time to add a .gitattributes file, but I won't be able to publish it until I get home (my company runs an artifactory server that intercepts npm publish)

@Dids
Copy link
Author

Dids commented Oct 27, 2017

Thank you! Not really an urgent issue, since it can be worked around, but definitely a nice thing to have.

@jcjolley
Copy link
Owner

If the .gitattributes file resolves your issue @Dids, please close this issue at your leisure. :)

@Dids
Copy link
Author

Dids commented Oct 28, 2017

Tested and verified working. :)

@Dids
Copy link
Author

Dids commented Dec 20, 2017

This still seems to be an issue, or was the npm package never updated?

@Dids Dids reopened this Dec 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants