Skip to content

JSX can't generate output file if it has absolute path on Windows #315

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

Closed
shibukawa opened this issue Apr 9, 2014 · 3 comments
Closed

Comments

@shibukawa
Copy link
Contributor

OK:

C:\Users\yoshi_000\dev\grunt-jsx>node_modules\.bin\jsx --output hello2 --executable node fixtures/hello2.jsx

C:\Users\yoshi_000\dev\grunt-jsx>node hello2
Hello, world! No.2

NG:

C:\Users\yoshi_000\dev\grunt-jsx>node_modules\.bin\jsx --output C:\Users\yoshi_000\hello2 --executable node fixtures/hello2.jsx

fs.js:642
  return binding.mkdir(pathModule._makeLong(path),
                 ^
Error: ENOENT, no such file or directory 'C:\Users\yoshi_000\dev\grunt-jsx\C:'
    at Object.fs.mkdirSync (fs.js:642:18)
    at Object.NodePlatform.mkpath$S (C:\Users\yoshi_000\dev\grunt-jsx\node_modules\jsx\bin\jsx:6245:11)
    at Object.NodePlatform.mkpath$S (C:\Users\yoshi_000\dev\grunt-jsx\node_modules\jsx\bin\jsx:6243:9)
    at Object.NodePlatform.mkpath$S (C:\Users\yoshi_000\dev\grunt-jsx\node_modules\jsx\bin\jsx:6243:9)
    at Object.NodePlatform.save$USS (C:\Users\yoshi_000\dev\grunt-jsx\node_modules\jsx\bin\jsx:6223:8)
    at JSXCommand$main$LPlatform$AS (C:\Users\yoshi_000\dev\grunt-jsx\node_modules\jsx\bin\jsx:6848:13)
    at Function._Main$main$AS (C:\Users\yoshi_000\dev\grunt-jsx\node_modules\jsx\bin\jsx:468:13)
    at Object.JSX.runMain (C:\Users\yoshi_000\dev\grunt-jsx\node_modules\jsx\bin\jsx:42813:15)
    at C:\Users\yoshi_000\dev\grunt-jsx\node_modules\jsx\bin\jsx:42855:5
    at Object.<anonymous> (C:\Users\yoshi_000\dev\grunt-jsx\node_modules\jsx\bin\jsx:42856:3)

C:\Users\yoshi_000\dev\grunt-jsx>
@kazuho
Copy link
Member

kazuho commented Apr 12, 2014

@shibukawa has this bug been fixed in #316?

@shibukawa
Copy link
Contributor Author

Yes, #316 is patch for this issue.

@kazuho
Copy link
Member

kazuho commented Apr 14, 2014

Thank you for closing the issue.

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

2 participants