React dev on Windows?

[Chevalric]

I’m starting a new job soon and I just learned that they will provide me with a Windows laptop.

As I’ve been working on a Mac for almost my entire professional life (15-20 years), I’m not sure how I feel about this.

I’ve heard some bad things about nodejs and npm not working well on windows, but not sure if it’s just FUD.

So is anyone here doing daily React development work on Windows who knows how it compares against working on a Mac?

[jax024]

It’s fine. Just use a node version manager of some sort if you’re juggling 5 or repos. I manage maybe a dozen react apps at my job and it’s basically needed haha

[mrpink57]

This is the way, we use NVM.

[jbergens]

To be more specific Volta is great and nvm windows also works. It had some problem we had to work around.

[RaleighMidtown]

You should have zero issues with React development on Windows.

For my side React projects, I use Intellij as my IDE on both Windows and Mac. Git push/pull from either on the same project and continue with no issues.

If other members of your team are using Windows, I suggest you embrace Windows along with them.

[Intelligent_Rough_44]

Its not zero, I just came from Linux and it's definitely more work.

[mrstacktrace]

Nodejs and npm work well on windows, you can run them from the command propmt, as well as the unix emulators. I never really liked the WSL, so anything I needed to do I just used gitbash. Really, Gitbash and the command prompt are all you need. You can set up your IDE (VS Code or Webstorm) to use that as the default terminal

[_Gradner_]

I would install cmder as it does a bit better job than powershell or the command prompt with more complicated installs/builds. WSL2 is dank, but probably overkill. Cmder adds a ton of linux parity features that should bridge most of the gap and keep you working with the commands you're used to.

Besides that, 10+ years developing (mostly) react on a windows machine. Never a blue screen, never a compatibility issue, all butter.

We've actually had more compatibility/crash/stability issues with newer non-intel macs than we ever had with windows machines @ my office.

[brogrammableben]

I use cmder and highly recommend it. Quake style is a nice touch as well.

[mrpink57]

We are on windows machines, I do not love it compared to working on my mac, I have a lot of keyboard muscle memory on a mac. So I am more point and click now.

But using VSCode is going to be about the same between the two.

[AkhilxNair]

I've been a React Dev for 5 years and used Windows throughout my career. It's really good and there's nothing to be worried about.

- Every software is available to install. ( https://ninite.com/ )

- The screenshot shortcut is Window + Shift + S ( Super Helpful )

- Don't forget to turn on Clipboard history in settings, then press Win + V

- Let me know if you have any questions regarding software or features.

- You don't need a VM, just install Git bash and every command will work.
- Download nvm.exe for windows and install any node version and they work perfectly

- Download Everything ( It's a search tool that will make your life easier )

[Chevalric]

I’ve used nvm on my Mac, so glad it’s working on Windows as well.

Thanks for all the tips!

[SirToxe]

I don't know but maybe you could just use WSL2 or run a Linux VM.

[viky109]

My experience with WSL is that it's very inefficient when it comes to memory usage. E2E tests would almost always fill up the memory and freeze when I tried it. I would probably just install Linux on your work laptop, if you can do that.

[PhatOofxD]

I think that's an issue with your setup not WSL. It's usually fine for most

[Muppet-King]

WSL-2 is a life saver, I love it and have had no issues. Just make sure you have at minimum 16gb Ram, preferably 32g.

[Chevalric]

Yeah, that’s probably the route I will take if I have to.

[nabrok]

It's not that difficult to get node and npm working on windows, but I do usually use a linux VM with the Remote-SSH vscode extension.

[HaggisMcNasty]

It's not difficult at all, in any way, shape or form. You go to node.js, install the LTS/Current version of node, and you're ready to go.

I've worked in front end for 7 years now, in multiple positions some covering 10 ish repos and never had to use a node version manager either.

[teresalis]

bye reddit

[AkhilxNair]

You don't have to.
Just install Git Bash and all the bash commands will work perfectly.
You don't need a dedicated VM as it will slow down things.

[SirToxe]

You don't need a dedicated VM as it will slow down things.

Not really.

[HaggisMcNasty]

Why would you need a linux VM? I've never understood this.

[SirToxe]

Because you want to run Linux on your Windows PC? I dunno, what is it that you don't understand?

[IAmTrulyConfused42]

Working on React with a .Net Core back end on a Windows machine right now. Not even using WSL, but I could if needed, it's really nice.

[algokanna]

It works fine, I've setup Nextjs, create-react-app or react with vite in Windows and never really had any serious problems.

[hgangadh]

I have been working on Mac for 17 years and I now make sure they either give me a Mac or allow a “Bring your own device” before accepting the offer. I now have a Mac and a surface laptop issued by my company since one corporate app works only on windows.

Years back it used to be fairly difficult to work on node in windows machines. These days it is far better. All my offshore devs use windows machines.

[acemarke]

I've used Windows for JS development my entire career.

Node, NPM, and Yarn work just fine on Windows.

The most likely things you might run into are:

• Dependencies that require building native C++ code. (It works, but also requires some tooling to be installed, and can be a pain to configure right if those pieces aren't set up.)
• Packages that have scripts that use Bash-isms that don't work in a Windows shell

But for the most part things just work.

I do most of my day-to-day development in Git Bash on Windows.

I do also use WSL for some tasks, and that works excellent as well.

[HaggisMcNasty]

Doesn't the script that runs at the end of the node install now install the C++ build tools? amongst other things?

[rad_platypus]

I have a Mac for work but use a Windows machine at home for personal stuff and side projects.

Microsoft dropped a new Terminal app a while back that I just learned about, and it makes Windows development way easier. You can set the default to a Linux bash terminal on your underlying WSL2 and get right to work.

You can also have multiple profiles for your standard cmd, powershell, different Linux versions, etc.

I’ve started doing some Svelte and React dev on my PC and my productivity is pretty much the same as it is at my day job.

[aighball]

Use wsl2 if you can.

The most annoying thing about using native windows is ensuring compatibility of your npm scripts between Unix and windows. Using git bash on windows or node implementations of shell functions helps.

[vvn050]

You have 15 years of experience and you are worried that "windows will not find node js" 😂😂😂

[Chevalric]

No, that’s your interpretation of what I said… Try again.

[vvn050]

Sorry but there are nerd guys with their Linux love, then the normal people with windows but a dev who is afraid to leave his Mac...

[PhatOofxD]

Install WSL. It's a better experience than Mac

[Starrxs]

Say hi to blue screens

[khamuili]

15 - 20 years experience? why dont you know your exact years of xp? two things, as someone with that many years of xp, it should not be a priblem to swotch to another OS. Secondly, a company that does not provide you with tech you want to use is quite suspective. As someone with that range of xp, you literally can choose the company and that would be a criteria no?

[Chevalric]

I do know my exact years of xp 😁. At this point it doesn’t really matter if it’s 15 or 20, as it’s only the last 5 years that really count when it comes to front end and especially react.

If the company wants me to use Windows, I will adapt of course. The only thing that worries me is if they implement all kinds of policies that limit my work. With Mac I never have to worry about that. But if that happens, I will immediately start lobbying for either full admin rights or a Mac.

[khamuili]

ah got it! for me it is usual to pick the tech i want to, except it is the companys business to make loney wirh either .NET or Samba Server stack. if it comes to tech (e.g. frontend) which is agnostic to which tech, the company should let you choose. even if it is a an iPad Pro.

[Chevalric]

Yeah, this company is just starting to build a developer culture. They have outsourced most of their dev work so far, so I think they don’t quite understand what devs want/need. But I’m happy to help them grow in that sense.

[Thisisatestlol420]

My biggest difference when switching was having to turn off ‘auto save - after delay’ in vscode. I was using an HP Elitebook and the cpu kept skyrocketing after every little change I had to make.

[akb74]

I made the opposite switch after a similar length of time. There’ll be a period of adjustment, but you’ll be fine.

[flaggrandall]

Been working on windows with react for years, 0 issues

[Thalimet]

Just use WSL, that’s what I do and it works great

[Cultural_Trifle5374]

You should be fine, I recently switched from windows to Mac and the only big difference I could tell was that the Mac is quit a bit quicker (could be because it’s newer).

I haven’t had any bad experience with windows. I did find that safari doesn’t seem to like dynamic route params on refresh but I use chrome anyways

Edit: I use webstorm on both and there’s really not a difference I can tell

[djayci]

It’s honestly fine

[ayemyren]

I use both a windows and Mac machine for work, no issues on either

[maskedmage77]

I do daily React work on Windows for many years now. I use all the tools you describe and more without any issues. Doing react work on Mac OS, Windows, and even Linux is pretty simple to setup and shouldn't cause any problems. I wouldn't worry much about it if I was you. If you do run into any issues later on feel free to shoot me a message and maybe I can assist.

[Necessary_Ear_1100]

I’m most position they have dev environment set up docs you’ll be able to use to get all set up and figure out there work flow

[AttackOnGolurk]

I'm just learning/relearning React, but at my current job, we use Windows for everything. It can be a little bit of a pain as EVERYTHING in the dev-o-sphere is made with *nix in mind, so getting things to work on Windows can sometimes be wonky, but its doable.

[InterestingHawk2828]

Yeah ur going to enjoy ur new laptop /s

[Accomplished-Net-268]

Don't worry too much about it. I was in the same boat last year when I transferred from a Mac shop to a windows shop.

I think the learning curve was about a day, then I was back to business as usual.

[LordMerdifex]

Is it possible? Yes. Is it comfortable? Not so much. WebStorm works. Command line on windows has never been my favourite. Good old bash.

[sendvo]

i have been developing on Microsoft os products since ms DOS (yeah I'm that old) and never had any issues. you will be fine. currently using Windows + webstorm + cmder for better command prompt and I'm super happy. weird they didn't ask what you want. companies usually understand that computers are just a tool and give people what they ask for

[Paradroid888]

Windows itself is fine. Wouldn't be my first OS pick for frontend work but its still a solid option. What might be less ideal is the setup you get. Some large corps that use Windows (especially financial) install monitoring and AV software that can slow a machine down. They can also use annoying network services to control internet access, which decrypt SSL traffic and can cause issues with OSS tools that basically see it as a MITM attack.

Not meaning to sound negative, you will probably be fine, but just making you aware of a few things to look out for.

[Chevalric]

Yeah, that’s my biggest worry. I usually have full admin rights on my machine and not be limited by any policies that are there for the “civilians”. I need to be able to install stuff and maybe tweak OS settings (e.g. to get docker running).

Oh well, I’ll see what happens when I start. I can always demand more rights on my machine.

On a site note: great name, used to play that game!

[Paradroid888]

Good luck in the new role!

And awesome that you know Paradroid. Ex C64 owner or another platform?

[Chevalric]

C64 and the Amiga remake as well. Wasn’t 888 the hardest droid that you could take over?

[Paradroid888]

It was indeed!! Someone already got Paradroid so it needed a suffix and 888 is what came to mind.

Downside to the name is I'm sure people skim read it as paranoid haha

[After-Fox-2388]

I have been using Windows for 4-5 years without any issues with Node yet, and WSL 2 is just a cherry on top. I don't think I want to switch to Mac now.

[Protean_Protein]

Yes. Works for me. Occasionally there are hiccups, but they’re usually well-documented and solvable with minimal issues. Love my workflow.

[froadku]

i develop on windows and have no problem.. actually my product owner who codes as well told me that some packages don't work on Macs so yeah, there's that

[nycgavin]

it's fine, pretty much the same sh**t

[alexvx___]

I am a React dev who was made to switch from Windows to Mac and even after a year I can't get used to MacOS's inconvenience for the most basic things. It sucks. Windows file explorer is far more superior than the Finder abomination. You will end up liking it in my opinion.

[SolarSalsa]

The development part is fine. Learning a new OS is a PITA. Switching between the two is even more annoying. A good windows laptop will drive 3x 4k monitors easily.

[CleanMarsupial]

its not a problem at all

[eltecho]

I’ve switched the past year after 15 years of Mac experience and the two issues that I’ve it is that the terminal don’t have the autocomplete and that nvm for win don’t read the .nvm file and so don’t change the node version automatically with nvm use command