Support for JavaScript being Disabled

tl; dr: Should I provide a way for developers to use the website portion of the product if they have JS disabled?

I am working a product idea where the primary user will be developers of all sorts (embedded, systems, desktop, web, mobile, game, ..) and one thing I have noticed throughout all the chats/forums/etc. that I have been involved in is that there is a certain percentage of them complaining about a website not being available because they have JS disabled and the site doesn't work, or there is "way too much JavaScript" and the site is (in their experience) slow and/or "bloated."

Even if I was to provide an alternate version for non-JS users it would be something that came after the initial launch, but something I would want to keep in my head during the primary development. I have done something like this before, but it was for a specific (internal to the customer) clientele that were limited in their browser and configuration. There was basically a job that ran each night to render a new static website with anything that changed during that day.

• Am I overthinking this?
• Is this one of those cases where I am trying to appease a type of user that would/may not be the kind of user I want in the first place?
• Does anyone have any experience in doing something like this?

Thanks,