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

Bug: npx oclif init fails on folder name with space #1367

Closed
ChazUK opened this issue Apr 12, 2024 · 0 comments · Fixed by #1368
Closed

Bug: npx oclif init fails on folder name with space #1367

ChazUK opened this issue Apr 12, 2024 · 0 comments · Fixed by #1368

Comments

@ChazUK
Copy link
Contributor

ChazUK commented Apr 12, 2024

Describe the bug
When running npm ini oclif on a folder that has a parent with a space in it, the chmod fails.

To Reproduce
Steps to reproduce the behavior:

  1. Create a folder structure with parent folders with spaces in ~/Development/Test Directory/repos/test/
  2. Run npx oclif init
  3. Go through prompts and then error occurs
$ npx oclif init
npx oclif init
Initializing oclif in /Users/username/Development/Test Directory/repos/test
? Command bin name the CLI will export test
? Select a topic separator spaces
? Select a module type ESM
? Select a package manager npm
Using module type ESM
Using package manager npm
Creating bin/dev.cmd
Creating bin/dev.js
Creating bin/run.cmd
Creating bin/run.js
    Error: Command failed: chmod +x /Users/username/Development/Test Directory/repos/test/bin/run.js
    chmod: /Users/username/Development/Test: No such file or directory
    chmod: Directory/repos/test/bin/run.js: No such file or directory

    Code: 1

Expected behavior
package.json etc updated along with bin folder

Your Environment (please complete the following information):

  • oclif/4.8.0 darwin-arm64 node-v20.11.1
  • OS & version: macOS Sonoma 14.4.1
  • terminal: zsh
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

Successfully merging a pull request may close this issue.

1 participant