alexanderGugel/ied

ied should create scripts in node_modules/.bin on Windows

Open

#119 opened on Apr 30, 2016

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (1,989 stars) (76 forks)batch import
help wantedwindows

Description

Currently ied creates directory junctions for the .bin symlinks on Windows (PR #95) - as junctions work only for directories, this does not work. As discussed in #95, symlinks require additional permissions on Windows, so it's a bad idea to use them.

ied should continue using directory junctions for the package directories, but for the .bin tools, it should follow what npm does on Windows - for each tool it creates 2 scripts:

  1. - a wrapper script for Cygwin/MSYS contexts
  2. .cmd - a wrapper script for native/any other context

Contributor guide

Tech stack
nodejs
Domain
cli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Node.js basicsWindows batch scriptingied codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Examine ied's current implementation for .bin symlinks on Windows (referenced in PR #95). Look at npm's approach of creating <tool> and <tool>.cmd wrapper scripts. Consider Windows specific scripting and permission requirements. Check any existing comments or linked issues for additional context.