Skip to content

Revise Node.js support and Vagrant provider details #319

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

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

Revise Node.js support and Vagrant provider details #319

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 6 additions & 8 deletions guides/appendix/common-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,11 +45,9 @@ See [The Windows Section](/release/appendix/windows/) for more details.

## Cygwin on Windows

Node.js on Cygwin is no longer supported [more
details](https://github.com/nodejs/node/wiki/Installation#building-on-cygwin)
Rather then using Cygwin, we recommend running Ember CLI natively on windows,
or via the new [Windows Subsystem
Linux](https://msdn.microsoft.com/en-us/commandline/wsl/install_guide).
Node.js on Cygwin or the [Windows Subsystem
Copy link
Contributor

@NullVoxPopuli NullVoxPopuli Dec 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why wouldn't we support wsl? It's just linux

Copy link
Author

@BryanH BryanH Dec 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Node doesn't support WSL without some extra work:

The Windows Subsystem for Linux (WSL) is not supported, but the GNU/Linux build process and binaries should work. .... Running the Windows binary (node.exe) in WSL will not work without workarounds such as stdio redirection. ↩

Linux](https://msdn.microsoft.com/en-us/commandline/wsl/install_guide) are [not supported](https://github.com/nodejs/node/blob/main/BUILDING.md#platform-list).
We recommend running Ember CLI natively on Windows.
Copy link
Contributor

@NullVoxPopuli NullVoxPopuli Dec 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I cannot recommend this, but we do support it

Copy link
Author

@BryanH BryanH Dec 31, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Running natively was in the original text:

Rather then using Cygwin, we recommend running Ember CLI natively on windows,

I edited the wording to align it to Node's supported platforms (WSL is problematic, as per the prior comment).
If that wasn't the intent, I'm happy to revert that change, just let me know.

Copy link
Contributor

@NullVoxPopuli NullVoxPopuli Dec 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is WSL problematic, since it's just linux, and linux is fully supported?

Copy link
Author

@BryanH BryanH Jan 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WSL is "problematic" because Node doesn't support running on WSL; they will not accept any bug reports for WSL-only issues. The Linux Node binaries should run, but there is no guarantee.

A workaround is to run the Windows binaries (e.g., node.exe) and use stdio redirection (">", "|", etc.) to keep any output in the WSL.


<!-- ## Usage with Docker -->
<!-- Possible topic for future development. -->
Expand Down Expand Up @@ -104,6 +102,6 @@ npm rebuild
### Provider

The two most common Vagrant providers, VirtualBox and VMware Fusion, will both
work. However, VMware Fusion is substantially faster and will use less battery
life if you're on a laptop. As of now, VirtualBox will use 100% of a single CPU
core to poll for file system changes inside of the VM.
work. However, VMware Fusion is substantially faster and consumes less energy
(important if running on laptop battery power). VirtualBox uses 100% of a single
CPU core to poll for file system changes inside of the VM.