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

Decide what to do with symlinks on Windows #65

Open
mbland opened this issue May 29, 2017 · 0 comments
Open

Decide what to do with symlinks on Windows #65

mbland opened this issue May 29, 2017 · 0 comments
Assignees

Comments

@mbland
Copy link
Owner

mbland commented May 29, 2017

Currently there are a few symbolic links to npm packages:

$ find public -type l
public/css/vendor/normalize.css
public/tests/vendor/chai.js
public/tests/vendor/mocha.css
public/tests/vendor/mocha.js
public/tests/vendor/sinon.js
public/vendor/es6-promise.auto.min.js

While current versions of Windows apparently support symlinks, they're still not that straightforward to work with:

So I'll need to decide whether to keep the symlinks as-is, or perhaps come up with another scheme for providing the files outside of the node_modules directory (e.g. just copying them).

@mbland mbland self-assigned this May 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant