Re: using npm_assets instead of browserify

To: debian-ruby@lists.debian.org
Subject: Re: using npm_assets instead of browserify
From: Pirate Praveen <praveen@onenetbeyond.org>
Date: Thu, 28 Jul 2016 01:08:15 +0530
Message-id: <[🔎] 2B698C8A-E9CC-4F6F-842B-BC4F1C84AD76@onenetbeyond.org>
In-reply-to: <[🔎] 63E8BE85-AF71-4B40-8569-97FFD57319C4@onenetbeyond.org>
References: <[🔎] 63E8BE85-AF71-4B40-8569-97FFD57319C4@onenetbeyond.org>

https://medium.com/technically-speaking/rails-react-browserify-e315001d5974#.you4k7h14

browserify-rails seems another method but node-browserify has long list of dependencies as well.

On 2016, ജൂലൈ 28 12:24:28 AM IST, Pirate Praveen <praveen@onenetbeyond.org> wrote:

https://github.com/GoodGuide/npm_assets/blob/master/README.markdown

Can anyone comment if this can be used instead of browserified js? For example, can we directly use node-handlebars instead of ruby-rails-assets-handlebars for diaspora using this method?

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Reply to:

References:
- using npm_assets instead of browserify
  - From: Pirate Praveen <praveen@onenetbeyond.org>

Prev by Date: using npm_assets instead of browserify
Next by Date: Re: gitlab, rails and stretch
Previous by thread: using npm_assets instead of browserify
Next by thread: gb ruby2.3_2.3.1-5 . armel
Index(es):
- Date
- Thread