CVE and update status of the FreeBSD ports tree3,295 unaddressed CVEs in 670 portsAll times are CET
Port details

www/rubygem-jsbundling-rails-rails71 1.3.1

Bundle and transpile JavaScript in Rails with esbuild, rollup.js, or Webpack

Port info

Maintainer
sunpoet@FreeBSD.org
Packages
latest: 1.3.1
Upstream
up to date
Last update
to 1.3.1 · a7ba0c40b5
Quarterly
2026Q4: 1.3.1
WWW
https://github.com/rails/jsbundling-rails
Links
cgit · VuXML · Report wrong data

Install

Package
# pkg install rubygem-jsbundling-rails-rails71
installs 1.3.1 from latest; from quarterly (2026Q4) 1.3.1
Port
# cd /usr/ports/www/rubygem-jsbundling-rails-rails71 && make install clean
Size
9.6 KiB download · 19 KiB installed
Depends on
devel/ruby-gems 4.0.21, lang/ruby34 3.4.9_2,1, www/rubygem-railties71 7.1.6
License
MIT

Packages by version and architecture

latest

FreeBSD versionamd64aarch64i386
FreeBSD 161.3.11.3.1–
FreeBSD 151.3.11.3.1–
FreeBSD 141.3.11.3.11.3.1

quarterly (2026Q4)

FreeBSD versionamd64aarch64i386
FreeBSD 151.3.11.3.1–
FreeBSD 141.3.11.3.11.3.1

version as in the ports tree (latest) or the most common one (quarterly) · different version · ✗ not built · – no packages for this platform. Package sets that have not been rebuilt for 60 days are left out.

Unaddressed and VuXML only (0)

No unaddressed CVE and nothing reported by pkg audit for the packaged version 1.3.1.

Fixed (0)

No VuXML entries for this package.

Problem reports (0) · open in Bugzilla, most recently changed first

None.

Commits (1)

Po-Chuan Hsieh (sunpoet) · 1.3.1
www/rubygem-jsbundling-rails-rails71: Add rubygem-jsbundling-rails-rails71 1.3.1

Import maps let you import JavaScript modules using logical names that map to
versioned/digested files -- directly from the browser. So you can build modern
JavaScript applications using JavaScript libraries made for ESM without the need
for transpiling or bundling.This frees you from needing Webpack, Yarn, npm, or
any other part of the JavaScript toolchain. All you need is the asset pipeline
that's already included in Rails.

With this approach you'll ship many small JavaScript files instead of one big
JavaScript file. Thanks to HTTP/2 that no longer carries a material performance
penalty during the initial transport, and in fact offers substantial benefits
over the long run due to better caching dynamics. Whereas before any change to
any JavaScript file included in your big bundle would invalidate the cache for
the the whole bundle, now only the cache for that single file is invalidated.

There's native support for import maps in Chrome/Edge 89+, and a shim available
for any browser with basic ESM support. So your app will be able to work with
all the evergreen browsers.
a7ba0c40b5