bcoe / awesome-cross-platform-nodejs Goto Github PK

Hey people,
We can adding more tools in CI list:

• github-actions
• gitlabCI

it might be smart to add a section that links to write-ups on known cross-platform problems.

Thanks for the suggestion @jamestalmage.

The current repository description is: A curated list of awesome developer tools and libraries for writing and testing code that runs on Windows and Linux.

While most cross-platform issues are Unix vs Windows, there are still few that are Mac-specific, e.g. when it comes to file watching or signals.

Also probably Node.js should be mentioned as well.

Alternatives descriptions could be:

• A curated list of awesome developer tools and libraries for writing and testing Node.js code that runs on Windows, MacOS and Linux.
• A curated list of awesome developer tools and libraries for writing and testing cross-platform Node.js code.

Most of the stuff offered here is pretty dense.

How about a few links that provide approachable but solid intros.

Here is one example that discusses paths: http://shapeshed.com/writing-cross-platform-node/

This is related to #27.

GitHub topics are important to make repositories easy to search/find and increase GitHub traffic.

I think adding as many topics as possible (20) is good too as it helps users finding the repository with alternative keywords.

@sindresorhus, @satazor in newish versions of Node.js, what issues continue to exist in spawn that would motivate the use of execa or cross-spawn. I wonder if:

1. some of the historic bugs have been addressed in Node.js.
2. if they haven't, could they be?

CC: @boneskull

Hi, appveyor.yml was removed from that repo.

I'd like to try out nvm-windows, and add it to this list:

https://github.com/coreybutler/nvm-windows?utm_source=nodeweekly&utm_medium=email

CC: @coreybutler

This is a requirement to submit on @sindresorhus awesome repository.

I am submitting an issue because I cannot edit GitHub topics myself.

@isaacs found that cross-spawn-async was a great option for cross-platform child_process.spawn().

Should we be explicit about the scope of this repository?

I suggest we add few checkboxes in the PR template such as:

• if you're adding a link, this should be related to cross-platform issues, i.e. OS-specific behavior. Also, those issues should not be solved in core Node.js.

This would discourage PRs about libraries that are cross-platform simply because they are built on top of Node.js which is (mostly) cross-platform.

Adding too many links not related to solving core Node.js cross-platform issues might also confuse readers like those comments on Reddit.

What do you think @bcoe? @sindresorhus?