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

No such file or directory on cli #77

Closed
Jameskmonger opened this issue Aug 12, 2016 · 11 comments
Closed

No such file or directory on cli #77

Jameskmonger opened this issue Aug 12, 2016 · 11 comments
Labels
Milestone

Comments

@Jameskmonger
Copy link
Contributor

When running alsatian from the command line in Ubuntu, I get:

: No such file or directory

This doesn't occur with gulp.

@jamesadarich
Copy link
Member

Ace @Jameskmonger, good to have this confirmed. Strange though because after we found this I put an integration test in that passes on Travis Linux and OSX.

Any ideas?

@Jameskmonger
Copy link
Contributor Author

Okay @jamesrichford, I've just cloned the latest copy of this repo and published it to npm under the name jkmalsatian, and that works fine. Looks like maybe the publish just got a bit borked up - probably just publish it again?

@jamesadarich
Copy link
Member

Which version did you have installed? Alpha.6?

@jamesadarich jamesadarich added this to the alpha.7 milestone Aug 12, 2016
@jamesadarich
Copy link
Member

@Jameskmonger just published alpha.7 - let me know if this works :)

@Jameskmonger
Copy link
Contributor Author

Odd. It doesn't look like this works. It seems like something that happens when it's published on your PC is causing it to break...

@jamesadarich
Copy link
Member

Hmmm... I take it that it's the file in the bin folder that's missing? Maybe it's a problem with my checkout of the repo?

I'll have to figure out about republishing, also need to figure out what's causing the problem so can add a script to prevent this issue in future.

I guess first step is to compare your npm package to mine! :)

@jamesadarich
Copy link
Member

Thinking maybe this is the problem!

npm/npm#12371

I'm going to change my git settings and try publishing alpha.8. Then if this solves it probably add a prepublilsh script to ensure line endings are set correctly.

@jamesadarich
Copy link
Member

jamesadarich commented Aug 13, 2016

Right @Jameskmonger - so I've got a potential fix in npm as alpha.8 so hopefully this resolves it - I've ensured that TypeScript compiles js with LF line endings :)

Let me know if there are any issues

@Jameskmonger
Copy link
Contributor Author

That's sorted it @jamesrichford - exactly what they said over at nodejs!

@jamesadarich jamesadarich modified the milestones: alpha.8, alpha.7 Aug 13, 2016
@jamesadarich
Copy link
Member

Nice one! Cheers for your help on this one mate!

@Jameskmonger
Copy link
Contributor Author

No worries @jamesrichford thanks for fixing it! I didn't notice any tsconfig changes for it (did you forget to push? or was it local system settings)

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