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.

Sign up for GitHub

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

Jump to bottom

Fix: sources should properly require dependencies for Node compatibility #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix: sources should properly require dependencies for Node compatibility #3

wants to merge 1 commit into from

Commits on Apr 25, 2022

  1. Main sources should properly require dependencies 

    Creating this largely as a discussion topic (since issues aren't open).    Can dependencies please be handled properly such that using this from `nodejs` "just works" - like with every NPM libraries - ie, libraries (in raw form) should require their own dependencies...  Users should not be forced to rely on globals just to use the library from Node proper.

I do think the final distributable would be improved if it also bundled `colorparsley` (a tiny dependency) rather than forcing client-side users to deal with dependency hell, but that's a secondary issue.

---

Also: Can the fact that this is a template repo be fixed and could issues be opposed to allow people to file issues?
    @joshgoebel
    joshgoebel committed Apr 25, 2022
    Configuration menu
    Copy the full SHA
    5d64057 View commit details
    Browse the repository at this point in the history