Nick Schonning

That's probably OK for your dev cycles, but those files were approved/edited by the language groups through direct PRs to the repo, and likely shouldn't be thrown away. I think...

Ah, if you're just wiping out the English files copies, that's great! There was an issue around cleaning those up awhile ago, but I don't think it got finish. FYI,...

I think https://github.com/nodejs/nodejs.org/pull/3056 was that initial push after the setup

@tniessen the API docs have been translated to a certain degree for some time over in https://github.com/nodejs/i18n, but never shipped as part of the website

Closing this, as the error is on the `.dev` site, and not the `.org` which this PR is against. `.org` doesn't have this problem. Thanks for creating the issue for...

No, the download URL comes from .org for both, but only https://nodejs.dev/en/ has this problem, not https://nodejs.org/en/

It's possible something in the Insider build is broken, I can reproduce your issue on `.dev` with both Firefox and Edge, but not on `.org`. PS: The solution isn't to...

> Could be. Or it could point to changes coming in the future where the user agent no longer includes that information. Definitely possible, but could also just a be...

That might make sense, but I'd suggest keeping the existing checks, and adding as the other `||`. Note that the site is currently mostly frozen while they try and merge...

> * nodejs.dev and nodejs.org live in different infrastructures with different bandwidth and resources (nodejs.dev lives on a free G Cloud server) PS: Minor, but I don't think that it's...