nodejs June 2021

nodejs@lists.fedoraproject.org

4 participants
3 discussions

Re: F35 Change: Node.js 16.x by default (System-Wide Change proposal)
by Stephen Gallagher 02 Jul '21

02 Jul '21

Just a quick reminder, this switch will be occurring in a little over three weeks, so make sure to test your NPM packages with Node.js 16.x! On Thu, Apr 29, 2021 at 3:46 PM Ben Cotton <bcotton(a)redhat.com> wrote: > > https://fedoraproject.org/wiki/Changes/Nodejs16 > > == Summary == > The latest release of Node.js to carry a 30-month lifecycle is the > 16.x series. As with 14.x, 12.x, 10.x and 8.x before it, Fedora 35 > will carry 16.x as the default Node.js interpreter for the system. The > 14.x and 12.x interpreters will remain available as non-default module > streams. > > == Owner == > * Name: [[User:zvetlik| Zuzana Svetlikova]] > * Email: zsvetlik(a)redhat.com > * Name: [[User:Sgallagh| Stephen Gallagher]] > * Email: sgallagh(a)fedoraproject.org > * Responsible SIG: Node.js SIG > > > > == Detailed Description == > Fedora 35 will ship with the latest LTS version of Node.js. '''dnf > install nodejs''' will give users nodejs-16.x and the matching npm > package. > > == Benefit to Fedora == > Node.js is a popular server-side JavaScript engine. Keeping Fedora on > the latest release allows us to continue tracking the state-of-the-art > in that space. For those whose applications do not yet work with the > 16.x release, Fedora 35 will also have the 14.x and 12.x releases > available as selectable module streams. > > == Scope == > * Proposal owners: The packages are already built for Fedora 33, 34 > and 35 in a non-default module stream. On June 14th, 2021, the > nodejs-16.x packages will be built in the non-modular repository and > thus become the default in Fedora 35. > > * Other developers: Any developer with a package that depends on > Node.js at run-time or build-time should test with the 16.x module > stream enabled as soon as possible. Issues should be reported to > nodejs(a)lists.fedoraproject.org > > * Release engineering: We will coordinate with the Node.js SIG to > create a side-tag to perform the rebuilds before making 16.x the > default. > * Policies and guidelines: N/A (not needed for this Change) > * Trademark approval: N/A (not needed for this Change) > > > == Upgrade/compatibility impact == > As with previous releases, users running Fedora 33 or Fedora 34 with > the non-modular nodejs-14.x packages will be automatically upgraded to > the 16.x packages when they upgrade to Fedora 35, which may cause > issues. If users are running software known not to support Node.js > 16.x yet, they can switch the system to use 14.x with '''dnf module''' > commands. > > == How To Test == > * Confirm that `dnf install nodejs` results in Node.js 16.x being installed. > * Confirm that upgrading from Fedora 33 or Fedora 34 with nodejs-14.x > installed (non-modular) results in an upgrade to nodejs-16.x > * Confirm that upgrading from Fedora 33 or Fedora 34 with the > `nodejs:14` module enabled does *not* result in an upgrade to 16.x and > still has `nodejs:14` enabled on Fedora 35. > * Confirm that upgrading from Fedora 33 or Fedora 34 with the > `nodejs:16` module enabled upgrades successfully and still has > `nodejs:16` enabled on Fedora 33. > > == User Experience == > Users will have the 16.x release of Node.js available by default. See > the "Upgrade/compatibility impact" section for specific details. > > == Dependencies == > All packages prefixed with `nodejs-` depend on this package. If they > do not work with Node.js 16.x, they will need to be updated, made > modular and dependent upon the `nodejs:14` stream or else removed from > Fedora 35. > > Prior to the switchover date to Node.js 16.x as the default, packagers > are strongly encouraged to test their existing Node modules with 16.x > via the Modular version by running: > > <pre> > dnf module reset nodejs > dnf module install nodejs:16/development > </pre> > > Packagers can also test their builds using `mock` by creating the file > `/etc/mock/fedora-rawhide-x86_64-nodejs16.cfg` with the following > contents: > > <pre> > config_opts['target_arch'] = 'x86_64' > config_opts['legal_host_arches'] = ('x86_64',) > config_opts['enable_disable_repos'] = ['--enablerepo', 'rawhide-modular'] > config_opts['module_install'] = ['nodejs:16/development'] > > include('templates/fedora-rawhide.tpl') > </pre> > > Then call > <pre> > mock -r fedora-rawhide-x86_64-nodejs16 --enablerepo=rawhide-modular nodejs-foo > </pre> > > (Note that the `--enablerepo=rawhide-modular` portion looks redundant, > but this is because of > [https://github.com/rpm-software-management/mock/issues/591 a mock > bug]) > > == Contingency Plan == > * Contingency mechanism: > Revert to Node.js 14.x as the default Node.js interpreter. This will > require bumping epoch. > > * Contingency deadline: Beta Freeze > * Blocks release? No > * Blocks product? No > > == Documentation == > * https://nodejs.org/dist/latest-v16.x/docs/api/ > * https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V16.md > > == Release Notes == > Fedora 35 now ships with Node.js 16.x as the default Node.js > JavaScript server-side engine. If your applications are not yet ready > for this newer version, you can revert to the 14.x series by running > the following commands > > <pre> > dnf remove nodejs > dnf module reset nodejs > dnf module install nodejs:14 > </pre> > > > -- > Ben Cotton > He / Him / His > Senior Program Manager, Fedora & CentOS Stream > Red Hat > TZ=America/Indiana/Indianapolis > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

1 2

Packaging - Plasma Browser Integration extension nodejs dependencies
by Onuralp SEZER 04 Jun '21

04 Jun '21

Hello all, Fedora KDE has a plasma-browser-integration[0] package it doesn't include the "actual browser" extension[1] in our repository. I want to add the plasma-browser-integration/firefox extension[2][3] "xpi" into the "plasma-browser-integration" package. However, I need to download the "web-ext"[4] package and a bunch of additional requirements in it. Is it ok to download all the requirements directly, show them as a separate source, get the xpi file directly, and delete the others, without doing package entire nodejs dependencies? What do you think? Am I missing some obvious solution, or is this a sane way forward? Any feedback and help would appreciate it. Current plasma browser integration spec: https://src.fedoraproject.org/rpms/plasma-browser-integration [0] : https://community.kde.org/Plasma/Browser_Integration [1] : https://addons.mozilla.org/en-US/firefox/addon/plasma-integration/ [2] : https://invent.kde.org/plasma/plasma-browser-integration [3] : https://invent.kde.org/plasma/plasma-browser-integration/-/tree/master/exte… [4] : https://www.npmjs.com/package/web-ext Thank you. Onuralp

4 4

should we try keep coffee-script ?
by Sérgio Basto 01 Jun '21

01 Jun '21

Hi, coffee-script is FTBFS on F34 (1), for update it we will need also update some other node packages , I don't know how many but at least 2 or 3 . So before I try , I'd like to know if it correct try maintain it ? @Patrick Vavrina your help is welcome . Best regards, (1) https://bugzilla.redhat.com/show_bug.cgi?id=1923684 -- Sérgio M. B.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

nodejs June 2021