Hi, I'm reporting that Fedora 30 (which was officially out 3~ days ago) isn't supported by the installer script.
On a fresh Fedora 30 Workstation installation, I've run the following command (found here):
curl -sL https://rpm.nodesource.com/setup_12.x | bash -
I ran into the following error and the installation failed.

This happened while trying to install NodeJS 12.x
Thanks!
can you post the output of lsb_release -a
@Tecardo1 Sure, here it is:

can you try running this:
uname -m
and this:
rpm -q --whatprovides redhat-release || rpm -q --whatprovides centos-release || rpm -q --whatprovides cloudlinux-release || rpm -q --whatprovides sl-release
want to see the output, right now i don't have a fedora 30 system here, but to note, i'm not dev or maintaining this scripts. It will make thinks more clear for the devs.
output for uname -m is x86_64
output for rpm -q --whatprovides redhat-release || rpm -q --whatprovides centos-release || rpm -q --whatprovides cloudlinux-release || rpm -q --whatprovides sl-release is fedora-release-common-30-1.noarch
try replacing this:
Line 216: DIST_VERSION=$(echo $DISTRO_PKG | sed -r 's/^[[:alpha:]]+-release(-server|-workstation|-client)?-([0-9]+).*$/\2/')
With
DIST_VERSION=$(echo $DISTRO_PKG | sed -r 's/^[[:alpha:]]+-release(-server|-workstation|-client|-common)?-([0-9]+).*$/\2/')
in the file, save it for that. Or use this file.
run it with bash - 'Script location'
did you install the normal fedora 30 workstation image?
@Tecardo1 Thanks for pitching in, I will try that when I get back to my comp.
Once I verify your changes as working, maybe someone from us can send a quick PR.
And yes, I'm using the normal workstation image downloaded from https://getfedora.org
Please report back if it works :)
@Tecardo1 I tried your change and got this:
## Installing the NodeSource Node.js 12.x repo...
## Inspecting system...
+ rpm -q --whatprovides redhat-release || rpm -q --whatprovides centos-release || rpm -q --whatprovides cloudlinux-release || rpm -q --whatprovides sl-release
+ uname -m
## Confirming "fc30-x86_64" is supported...
+ curl -sLf -o /dev/null 'https://rpm.nodesource.com/pub_12.x/fc/30/x86_64/nodesource-release-fc30-1.noarch.rpm'
## Your distribution, identified as "fedora-release-common-30-1.noarch", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support
Indeed they don't provide the rpm packages for fedora 30 right now. 28 and 29 are included only. Didnt check that, sorry :)
Just found out: For Fedora 29, the release URL of the RPM repo was:
https://rpm.nodesource.com/pub_12.x/fc/29/x86_64/nodesource-release-fc29-1.noarch.rpm
So, for Fedora 30, it should be:
https://rpm.nodesource.com/pub_12.x/fc/30/x86_64/nodesource-release-fc30-1.noarch.rpm
But if you look here, you won't see "30" as a available directory indicating that releases aren't prepped for Fedora 30 yet.
All this might have been a moot discovery but I found this out while hacking the official installation script to see what it was doing.
Fingers crossed for faster Node 12 release on Fedora 30 (also Docker-CE for F30 isn't available yet :( ).
As mentioned there is no Node 12 release for Fedora 30. But there isn't any release for fedora 30.
Any update on this? From what I see above modifying the installer does not help because the rpm is not available on the server. Is there a way we can help building those rpm's so they are updated faster on the server?

Isn't the 29 rpm package companies with 30 already?
I wonder why its printing .noarch when I'm running on x86_64 platform. I was trying with the 8.x script
Installing the Fedora 29 repo worked for me on 30... so far. If anyone else can't wait for the 30 package to be released:
sudo dnf install https://rpm.nodesource.com/pub_12.x/fc/29/x86_64/nodesource-release-fc29-1.noarch.rpm
sudo dnf install nodejs
Right now there isn't much activity in here. Don't know what's happening, but your way could break things.
Also, if you're tired of all this (like I am). Simply start using NVM (https://github.com/nvm-sh/nvm) instead, which is every bit as good if not better.
Considering that Fedora 28 is now officially end-of-life, hopefully they will get the official package for 30 ready soon.
Now in Docker
FROM fedora:latest is 30, build not working.
From Jun 14 the rpm repositories exists, see here for 10.x or here for 12.x
sudo dnf install https://rpm.nodesource.com/pub_12.x/fc/30/x86_64/nodesource-release-fc30-1.noarch.rpm
sudo dnf intall nodejs
works.
Seem that only the fix for the script is missing.
The instructions at https://github.com/nodesource/distributions/#rpminstall now work as expected --I was able to install Node 12 on Fedora 30 Workstation, so closing this issue, thanks for the fix.
The instructions at https://github.com/nodesource/distributions/#rpminstall now work as expected --I was able to install Node 12 on Fedora 30 Workstation, so closing this issue, thanks for the fix.
just FYI, NOK for Node 8 for me, in a Fedora 30 container:
FROM fedora:30
RUN curl -sL https://rpm.nodesource.com/setup_8.x | bash -
causes:
STEP 4: RUN curl -sL https://rpm.nodesource.com/setup_8.x | bash -
tput: No value for $TERM and no -T specified
## Installing the NodeSource Node.js 8.x LTS Carbon repo...
## Inspecting system...
+ rpm -q --whatprovides redhat-release || rpm -q --whatprovides centos-release || rpm -q --whatprovides cloudlinux-release || r
pm -q --whatprovides sl-release
+ uname -m
## Could not determine your distribution version, you may not be running a supported version of Enterprise Linux. Please contac
t NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect. Include your 'distribution p
ackage' name: fedora-release-common-30-5.noarch.
Error: error building at STEP "RUN curl -sL https://rpm.nodesource.com/setup_8.x | bash -": error while running runtime: exit status 1
using NVM (https://github.com/nvm-sh/nvm) instead,
Yeah that one works for me, so no action needed on this, just wanted to let you know.
BTW: Fedora 30 is also not mentioned on the README.
Most helpful comment
Also, if you're tired of all this (like I am). Simply start using NVM (https://github.com/nvm-sh/nvm) instead, which is every bit as good if not better.