Yarn is a new node package manager that replaces the existing workflow for the
npm client or other package managers while remaining compatible with the npm
registry. It has the same feature set as existing workflows while operating
faster, more securely, and more reliably.
Affects: users of USES=nodejs, www/node*, www/npm* and www/yarn*
Author: sunpoet@FreeBSD.org
Reason:
The current USES=nodejs has the following issues:
- www/node is not the default version while www/node16 is.
- It also means inconsistent naming of node ports.
- www/npm duplicates with www/npm-node16.
- www/yarn duplicates with www/yarn-node16.
The notable changes are introduced to fix the above issues:
- Rewrite Mk/Uses/nodejs.mk.
- Add new LTS version of nodejs (www/node18).
- Add new current version of nodejs (www/node19).
- Change default nodejs version from 16 to 18 (latest LTS),
- Use consistent naming for all supported node versions.
- Convert www/node, www/npm and www/yarn to meta ports.
After these changes:
- All supported node versions are named as node{14,16,18,19}.
- www/node is a meta port which depends on the default version
(e.g. www/node18)
- www/npm is a meta port which depends on the default version
(e.g. www/npm-node18)
- www/yarn is a meta port which depends on the default version
(e.g. www/yarn-node18)
Reason:
The port framework was updated to use a default version for nodejs.
The default version is pointing to the latest LTS version which is
currently version 16.
You can overwrite this by defining in /etc/make.conf, e.g. version 17:
DEFAULT_VERSIONS=nodejs=17
Or if you would like to stick always to the current version use:
DEFAULT_VERSIONS=nodejs=current
If you would like to use yarn or npm together with nodejs version 17,
just install the package that is pulling the wanted dependency to nodejs:
# pkg install yarn-node17
# pkg install npm-node17
Framework: Rewrite nodejs.mk and reorganize www/{node,npm,yarn}
The current USES=nodejs has the following issues:
- www/node is not the default version while www/node16 is.
- It also means inconsistent naming of node ports.
- www/npm duplicates with www/npm-node16.
- www/yarn duplicates with www/yarn-node16.
The notable changes are introduced to fix the above issues:
- Rewrite Mk/Uses/nodejs.mk.
- Add new LTS version of nodejs (www/noe18).
- Add new current version of nodejs (www/node19).
- Change default nodejs version from 16 to 18 (latest LTS).
- Use consistent naming for all supported node versions.
- Convert www/node, www/npm and www/yarn to meta ports.
After this commit:
- All supported node versions are named as node{14,16,18,19}
- www/node is a meta port which depends on the default version (e.g. www/node18)
- www/npm is a meta port which depends on the default version (e.g.
www/npm-node18)
- www/yarn is a meta port which depends on the default version (e.g.
www/yarn-node18)
- Bump PORTREVISION of dependent ports for dependency change (from www/node16 to
www/node18)
Discussed with: jrm, otis, pizzamig
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
*/*: use new nodejs USES flag
Simply define which nodejs version is required using the nodejs USES flag.
PR: 259783
Differential Revision: https://reviews.freebsd.org/D32790
www/yarn: make yarn-node16 available
Currently many node packages do not support node 17 which is
used for www/node.
This for example fixes the usage of www/gitlab-ce which cannot
run the upgrade step if node 17 is used.
PR: 259475
PR: 259476
PR: 259477
Approved by: pizzamig (maintainer)
Mark ports recursively depending on Python 2.7 for expiration on June 23.
For ports optionally dependending on Python 2.7, just mark those options
as expired. Remove konquerer from the x11/kde-baseapps metaport and bump
its PORTREVISION.
Submitted by: rene
Reviewed by: portmgr, adridg, ehaupt, lme, madpilot, pizzamig, se, sunpoet, yuri
Approved by: portmgr
Differential Revision: https://reviews.freebsd.org/D28665
www/yarn: Use www/node as default
To be synced with other porst, yarn will use www/node
Reported by: jrm
Approved by: olivier (mentor)
Differential Revision: https://reviews.freebsd.org/D13037
www/yarn: update to 1.1.0 and fix the yarn script
Re-enabling the readlink -f option on FreeBSD
Update to version 1.1.0
PR: 222696
Approved by: olivier (mentor)
Differential Revision: https://reviews.freebsd.org/D12542
www/yarn: Updating to version 1.0.2
Adopting a more fine grained conflict type
Fixing a Linux incompatibility
Approved by: olivier (mentor)
Differential Revision: https://reviews.freebsd.org/D12516
www/yarn: Updating to version 1.0.1
Adding an option to avoid the installation of the yarn script, that
collides with a hadoop2 utility
Approved by: olivier (mentor)
Differential Revision: https://reviews.freebsd.org/D12332
www/yarn: Update to version 0.24.6
Other changes:
- Patch package.json to show installation was via package [1]
- Set executable bit for JavaScript scripts requiring it [1]
- Do not install Windows binaries
- Use fully qualified paths to create links in ${PREFIX}/bin/ [2]
- Create link for yarnpkg in ${PREFIX}/bin [1]
Upstream releases: https://github.com/yarnpkg/yarn/releases
Reviewed by: jlduran@gmail.com [1], mat [2]
Approved by: luca.pizzamiglio@gmail.com (maintainer),
swills (mentor, implicit)
Differential Revision: https://reviews.freebsd.org/D10696
Switch the default yarn node backend from node6 (LTS) to node (current).
This makes yarn's backend selection consistent with npm and all other
node consumers.
Add an UPDATING message to reduce surprise.
Submitted by: maintainer (Luca Pizzamiglio)
Reported by: jrm
New port: www/yarn
Yarn is a new node package manager that replaces the existing workflow for the
npm client or other package managers while remaining compatible with the npm
registry. It has the same feature set as existing workflows while operating
faster, more securely, and more reliably.
PR: 218521
Submitted by: luca.pizzamiglio@gmail.com