head	1.2;
access;
symbols
	pkgsrc-2026Q1:1.2.0.2
	pkgsrc-2026Q1-base:1.2
	pkgsrc-2025Q4:1.1.0.2
	pkgsrc-2025Q4-base:1.1;
locks; strict;
comment	@# @;


1.2
date	2026.01.18.15.12.12;	author taca;	state Exp;
branches;
next	1.1;
commitid	E63QJQGf7rwg2TqG;

1.1
date	2025.11.03.06.04.31;	author taca;	state Exp;
branches;
next	;
commitid	SAvBZHu7U08Pr4hG;


desc
@@


1.2
log
@www/ruby-importmap-rails: update to 2.2.3

2.2.3 (2026-01-07)

What's Changed

* Fix pin_all_from incorrectly removing "js" substring from filenames by
  @@rafaelfranca in #313
* Handle package names with nested paths in import maps by @@rafaelfranca in
  #322
@
text
@# $NetBSD: Makefile,v 1.1 2025/11/03 06:04:31 taca Exp $

DISTNAME=	importmap-rails-2.2.3
CATEGORIES=	www

MAINTAINER=	pkgsrc-users@@NetBSD.org
HOMEPAGE=	https://github.com/rails/importmap-rails
COMMENT=	Use ESM with importmap to manage modern JavaScript in Rails
LICENSE=	mit

#DEPENDS+=	${RUBY_ACTIVESUPPORT_DEPENDS}
#DEPENDS+=	${RUBY_ACTIONPACK_DEPENDS}
DEPENDS+=	${RUBY_RAILTIES_DEPENDS}

#
# This pacakge is for redmine61
#
RUBY_RAILS_ACCEPTED=	72

USE_LANGUAGES=	# none

.include "../../lang/ruby/gem.mk"
.include "../../mk/bsd.pkg.mk"
@


1.1
log
@www/ruby-importmap-rails: add version 2.2.2

This package is required by forthcoming ruby-redmin61 package.

# Importmap for Rails

[Import maps](https://github.com/WICG/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 ES modules (ESM) without the need for
transpiling or
bundling](https://world.hey.com/dhh/modern-web-apps-without-javascript-bundling-or-transpiling-a20f2755).
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 whole bundle, now only the cache for that
single file is invalidated.

[Import maps are supported natively in all major, modern
browsers](https://caniuse.com/?search=importmap).  If you need to work with
legacy browsers without native support, you can explore using [the shim
available](https://github.com/guybedford/es-module-shims).
@
text
@d1 1
a1 1
# $NetBSD$
d3 1
a3 1
DISTNAME=	importmap-rails-2.2.2
@