Add rubygem-webpacker-rails60 4.2.2 (copied from rubygem-webpacker-rails5)
This commit is contained in:
parent
d6898bd7f7
commit
688da51d69
Notes:
svn2git
2021-03-31 03:12:20 +00:00
svn path=/head/; revision=525374
4 changed files with 38 additions and 0 deletions
|
@ -6506,6 +6506,7 @@
|
|||
SUBDIR += rubygem-webfinger
|
||||
SUBDIR += rubygem-webpacker-rails5
|
||||
SUBDIR += rubygem-webpacker-rails50
|
||||
SUBDIR += rubygem-webpacker-rails60
|
||||
SUBDIR += rubygem-will_paginate
|
||||
SUBDIR += rubygem-windows_error
|
||||
SUBDIR += rubygem-wisper
|
||||
|
|
25
devel/rubygem-webpacker-rails60/Makefile
Normal file
25
devel/rubygem-webpacker-rails60/Makefile
Normal file
|
@ -0,0 +1,25 @@
|
|||
# $FreeBSD$
|
||||
|
||||
PORTNAME= webpacker
|
||||
PORTVERSION= 4.2.2
|
||||
CATEGORIES= devel rubygems
|
||||
MASTER_SITES= RG
|
||||
PKGNAMESUFFIX= -rails60
|
||||
|
||||
MAINTAINER= sunpoet@FreeBSD.org
|
||||
COMMENT= Use Webpack to manage app-like JavaScript modules in Rails
|
||||
|
||||
LICENSE= MIT
|
||||
LICENSE_FILE= ${WRKSRC}/MIT-LICENSE
|
||||
|
||||
RUN_DEPENDS= rubygem-activesupport60>=4.2:devel/rubygem-activesupport60 \
|
||||
rubygem-rack-proxy>=0.6.1:www/rubygem-rack-proxy \
|
||||
rubygem-railties60>=4.2:www/rubygem-railties60 \
|
||||
yarn:www/yarn
|
||||
|
||||
USES= gem
|
||||
USE_RUBY= yes
|
||||
|
||||
NO_ARCH= yes
|
||||
|
||||
.include <bsd.port.mk>
|
3
devel/rubygem-webpacker-rails60/distinfo
Normal file
3
devel/rubygem-webpacker-rails60/distinfo
Normal file
|
@ -0,0 +1,3 @@
|
|||
TIMESTAMP = 1580562345
|
||||
SHA256 (rubygem/webpacker-4.2.2.gem) = 52b14bce1882b7024c8dbb6820b2813e3ed01652b5fa0f88b7ed52be4cf3a940
|
||||
SIZE (rubygem/webpacker-4.2.2.gem) = 223232
|
9
devel/rubygem-webpacker-rails60/pkg-descr
Normal file
9
devel/rubygem-webpacker-rails60/pkg-descr
Normal file
|
@ -0,0 +1,9 @@
|
|||
Webpacker makes it easy to use the JavaScript preprocessor and bundler Webpack
|
||||
to manage application-like JavaScript in Rails. It coexists with the asset
|
||||
pipeline, as the primary purpose for Webpack is app-like JavaScript, not images,
|
||||
css, or even JavaScript Sprinkles (that all continues to live in app/assets). It
|
||||
is, however, possible to use Webpacker for CSS and images assets as well, in
|
||||
which case you may not even need the asset pipeline. This is mostly relevant
|
||||
when exclusively using component-based JavaScript frameworks.
|
||||
|
||||
WWW: https://github.com/rails/webpacker
|
Loading…
Reference in a new issue