sync/ports
1
0
Fork 0
mirror of https://git.freebsd.org/ports.git synced 2025-04-28 01:26:39 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

www/rubygem-jsbundling-rails-rails72: Add rubygem-jsbundling-rails-rails72 1.3.1 (copied from rubygem-jsbundling-rails)

Browse source
This commit is contained in:
Po-Chuan Hsieh 2025-01-03 00:28:54 +08:00
parent 80a89eea52
commit 1c99761f8f
No known key found for this signature in database
GPG key ID: 9A4BD10F002DD04B
4 changed files with 36 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
www/Makefile
View file

@ -2146,6 +2146,7 @@
SUBDIR += rubygem-jsbundling-rails
SUBDIR += rubygem-jsbundling-rails-rails70
SUBDIR += rubygem-jsbundling-rails-rails71
SUBDIR += rubygem-jsbundling-rails-rails72
SUBDIR += rubygem-jsobfu
SUBDIR += rubygem-json-jwt
SUBDIR += rubygem-json-jwt-gitlab

20
www/rubygem-jsbundling-rails-rails72/Makefile Normal file
View file

@ -0,0 +1,20 @@
PORTNAME= jsbundling-rails
PORTVERSION= 1.3.1
CATEGORIES= www rubygems
MASTER_SITES= RG
PKGNAMESUFFIX= -rails72
MAINTAINER= sunpoet@FreeBSD.org
COMMENT= Bundle and transpile JavaScript in Rails with esbuild, rollup.js, or Webpack
WWW= https://github.com/rails/jsbundling-rails
LICENSE= MIT
LICENSE_FILE= ${WRKSRC}/MIT-LICENSE
RUN_DEPENDS= rubygem-railties72>=6.0.0:www/rubygem-railties72
USES= gem
NO_ARCH= yes
.include <bsd.port.mk>

3
www/rubygem-jsbundling-rails-rails72/distinfo Normal file
View file

@ -0,0 +1,3 @@
TIMESTAMP = 1722711339
SHA256 (rubygem/jsbundling-rails-1.3.1.gem) = 0fa03f6d051c694cbf55a022d8be53399879f2c4cf38b2968f86379c62b1c2ca
SIZE (rubygem/jsbundling-rails-1.3.1.gem) = 10752

12
www/rubygem-jsbundling-rails-rails72/pkg-descr Normal file
View file

@ -0,0 +1,12 @@
Use esbuild, rollup.js, or Webpack to bundle your JavaScript, then deliver it
via the asset pipeline in Rails. This gem provides installers to get you going
with the bundler of your choice in a new Rails application, and a convention to
use app/assets/builds to hold your bundled output as artifacts that are not
checked into source control (the installer adds this directory to .gitignore by
default).
You develop using this approach by running the bundler in watch mode in a
terminal with yarn build --watch (and your Rails server in another, if you're
not using something like puma-dev). You can also use ./bin/dev, which will start
both the Rails server and the JS build watcher (along with a CSS build watcher,
if you're also using cssbundling-rails).