Rails asset pipeline - referencing vendor/lib plugin manifest files from the application manifest files -
Rails asset pipeline - referencing vendor/lib plugin manifest files from the application manifest files -
theory
the rails guides can this
http://guides.rubyonrails.org/asset_pipeline.html
2.2.2 using index files
sprockets uses files named index (with relevant extensions) special purpose.
for example, if have jquery library many modules, stored in lib/assets/library_name, file lib/assets/library_name/index.js serves manifest files in library. file include list of required files in order, or simple require_tree directive.
the library whole can accessed in application manifest so: //= require library_name
this simplifies maintenance , keeps things clean allowing related code grouped before inclusion elsewhere.
error
so i'm trying have manifest files plugin in vendor folder. it's not working, saying in browser
couldn't find file 'multipurpose_bookshelf'
code
this originates application.js manifest file
app/assets/javascripts/application.js
//= require multipurpose_bookshelf which according rails guides, should reference folder named multipurpose_bookshelf rather rather multipurpose_bookshelf.js file in normal asset paths under javascripts folder.
the same should true css files
app/assets/javascripts/application.css.scss
/*= require multipurpose_bookshelf */ should reference index.js or index.css files, respectively, in these locations
vendor/assets/multipurpose_bookshelf/multipurpose_bookshelf.index.js
//= require js/jquery.bookshelf_slider.min //= require js/easing.1.3 //= require js/ //= require js/ex_skin02 vendor/assets/multipurpose_bookshelf/multipurpose_bookshelf.index.css
/* *= require bookshelf_slider *= require skin02 * */ what missing? how application manifest file correctly reference vendor manifest files?
ruby-on-rails asset-pipeline
Comments
Post a Comment