www/tailwindcss4: Improve loader & inject default NODE_PATH
Double-bump PORTREVISION because a private one is in use in some places.
Update a bunch of flags that broke in the latest npm update.
This simplifies most use cases to just modify the tailwind calling path,
and as a bonus it makes the testing simpler too. Most of the tests are
failure cases identified during using tailwind against
https://phoenixframework.org/ testing.
Sponsored by: SkunkWerks, GmbH
Event: EuroBSDcon 2026
www/tailwindcss3: Fix build after npm update
No PORTREVISION bump required, as there are no functional changes
Sponsored by: SkunkWerks, GmbH
Reported by: Poudriere
Event: EuroBSDcon 2026
devel/electron42: Use esbuild binary provided by npm package registry
The chromium upstream expects a specific version of esbuild for
building, which is sometimes different from the one we have in the
ports tree. To prevent such a discrepancy, always use the binary of
the same version as the upstream one which is provided by the npm
package registry.
Reported by: Andrea Venturoli <ml at netfence.it> (via ports)
(cherry picked from commit c8ee96bf65adf08ff9c8a7a87cc7829eeb4858d3)
devel/electron44: Use esbuild binary provided by npm package registry
The chromium upstream expects a specific version of esbuild for
building, which is sometimes different from the one we have in the
ports tree. To prevent such a discrepancy, always use the binary of
the same version as the upstream one which is provided by the npm
package registry.
Reported by: Andrea Venturoli <ml at netfence.it> (via ports)
devel/electron41: Use esbuild binary provided by npm package registry
The chromium upstream expects a specific version of esbuild for
building, which is sometimes different from the one we have in the
ports tree. To prevent such a discrepancy, always use the binary of
the same version as the upstream one which is provided by the npm
package registry.
Reported by: Andrea Venturoli <ml at netfence.it> (via ports)
devel/electron43: Use esbuild binary provided by npm package registry
The chromium upstream expects a specific version of esbuild for
building, which is sometimes different from the one we have in the
ports tree. To prevent such a discrepancy, always use the binary of
the same version as the upstream one which is provided by the npm
package registry.
Reported by: Andrea Venturoli <ml at netfence.it> (via ports)
devel/electron42: Use esbuild binary provided by npm package registry
The chromium upstream expects a specific version of esbuild for
building, which is sometimes different from the one we have in the
ports tree. To prevent such a discrepancy, always use the binary of
the same version as the upstream one which is provided by the npm
package registry.
Reported by: Andrea Venturoli <ml at netfence.it> (via ports)
devel/electron40: Use esbuild binary provided by npm package registry
The chromium upstream expects a specific version of esbuild for
building, which is sometimes different from the one we have in the
ports tree. To prevent such a discrepancy, always use the binary of
the same version as the upstream one which is provided by the npm
package registry.
Reported by: Andrea Venturoli <ml at netfence.it> (via ports)
games/anki: Update to 26.09
* Migrate to Yarn v4 to be in sync with upstream. To ensure that the
preinstalled Yarn v4 is actually used, a few minor workarounds and a
new variable PREINSTALLED_YARN are required.
The latter is necessary because, with Yarn v2 and newer, environment
variables prefixed with YARN_ can no longer be used.
* Sort pkg-plist while I'm here.
Changelog:
https://github.com/ankitects/anki/releases/tag/26.09
MFH: 2026Q3
Security: ce54d883-b060-11f1-b187-901b0edee044
(cherry picked from commit 65434f71218e5a8114ea642231acaeb609ced7bd)
games/anki: Update to 26.08
* Switch to USES=npm and adjust/remove the relevant parts.
Although Yarn v4 is already being used according to "package.json",
stick with Yarn v1 for now to complete a 1:1 migration from the before
to the after state with respect to the used tools during build.
Changelog:
https://github.com/ankitects/anki/releases/tag/26.08
(cherry picked from commit 9b3e128970f2c53a39eed9b0157514459a5b131f)
