| Port details |
- rubygem-jsbundling-rails Bundle and transpile JavaScript in Rails with esbuild, rollup.js, or Webpack
- 1.0.3 www
 =0      Version of this port present on the latest quarterly branch. - Maintainer: sunpoet@FreeBSD.org
- Port Added: 2022-01-11 18:56:04
- Last Update: 2022-09-07 21:58:51
- Commit Hash: fb16dfe
- Also Listed In: rubygems
- License: MIT
- Description:
- 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).
 –  –  –  –  - pkg-plist: as obtained via:
make generate-plist - Dependency lines:
-
- rubygem-jsbundling-rails>0:www/rubygem-jsbundling-rails
- To install the port:
- cd /usr/ports/www/rubygem-jsbundling-rails/ && make install clean
- To add the package, run one of these commands:
- pkg install www/rubygem-jsbundling-rails
- pkg install rubygem-jsbundling-rails
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: rubygem-jsbundling-rails
- Flavors: there is no flavor information for this port.
- distinfo:
- TIMESTAMP = 1655829882
SHA256 (rubygem/jsbundling-rails-1.0.3.gem) = aa64e9096d7316550d25e04f01e31ad7d40bb6074b3a80e0abe49cc9ea41a4fa
SIZE (rubygem/jsbundling-rails-1.0.3.gem) = 9728
- Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- ruby30 : lang/ruby30
- gem : devel/ruby-gems
- Runtime dependencies:
-
- rubygem-railties70>=6.0.0 : www/rubygem-railties70
- ruby30 : lang/ruby30
- gem : devel/ruby-gems
- Patch dependencies:
-
- ruby30 : lang/ruby30
- gem : devel/ruby-gems
-
- This port is required by:
- for Run
-
- www/rubygem-rails70
- Configuration Options:
- No options to configure
- Options name:
- www_rubygem-jsbundling-rails
- USES:
- gem
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
| Commit History - (may be incomplete: see SVNWeb link above for full details) |
| Commit | Credits | Log message |
|---|
07 Sep 2022 21:58:51
 |
Stefan Eßer (se) |
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) |
1.0.3
07 Sep 2022 21:10:59
|
Stefan Eßer (se) |
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  ) |
1.0.3
20 Jul 2022 14:23:26
|
Tobias C. Berner (tcberner) |
www: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
*
* <hvo.pm@xs4all.nl>
* Aaron Dalton <aaron@FreeBSD.org>
* Aaron Dalton <aaron@daltons.ca>
* Aaron LI <aly@aaronly.me>
* Aaron Zauner <az_mail@gmx.at>
* Abel Chow <achow@transoft.net>
* Adam Weinberger <adamw@FreeBSD.org>
* Ade Lovett <ade@FreeBSD.org>
* Adrian Steinmann <ast@marabu.ch>
* Akinori MUSHA aka knu <knu@idaemons.org> (Only the first 15 lines of the commit message are shown above ) |
1.0.3
21 Jun 2022 20:58:30
|
Po-Chuan Hsieh (sunpoet) |
www/rubygem-jsbundling-rails: Update to 1.0.3
Changes: https://github.com/rails/jsbundling-rails/releases |
1.0.2
25 Mar 2022 13:37:42
|
Po-Chuan Hsieh (sunpoet) |
www/rubygem-jsbundling-rails: Update to 1.0.2
Changes: https://github.com/rails/jsbundling-rails/releases |
1.0.1
07 Mar 2022 18:13:07
|
Po-Chuan Hsieh (sunpoet) |
www/rubygem-jsbundling-rails: Update to 1.0.1
Changes: https://github.com/rails/jsbundling-rails/releases |
1.0.0
11 Jan 2022 18:43:49
|
Po-Chuan Hsieh (sunpoet) |
www/rubygem-jsbundling-rails: Add rubygem-jsbundling-rails 1.0.0
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).
WWW: https://github.com/rails/jsbundling-rails |
As an Amazon Associate I earn from qualifying purchases.