normalize-rails icon indicating copy to clipboard operation
normalize-rails copied to clipboard

File to import not found or unreadable: normalize-rails/normalize

Open kvokka opened this issue 8 years ago • 7 comments

File to import not found or unreadable: normalize-rails/normalize.
Load paths:
~/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/normalize-rails-3.0.3/vendor/assets/stylesheets

Error with asset pipeline only

kvokka avatar Apr 22 '16 02:04 kvokka

@kvokka What version of Rails are you using?

hirokishirai avatar Jun 28 '16 16:06 hirokishirai

4.2.6

kvokka avatar Jun 28 '16 16:06 kvokka

Not working for Rails 4.2.6 too

Ihor912 avatar Aug 11 '16 08:08 Ihor912

@kvokka @Igor912 I create a test rails app and install normalize-rails on it. Then, there is no problem. Probably, You have to use normalize-rails is version 4.1.1.

  • rails: 4.2.6
  • ruby: 2.3.0
mkdir test-normalize-rails
cd test-normalize-rails
bundle init
vi Gemfile
- # gem 'rails'
+ gem 'rails', '4.2.6'
bundle install --path vendor/bundle
bundle exec rails new . --skip-bundle
vi Gemfile
+ gem 'normalize-rails'
bundle install # In the second and subsequent bundle install, path specification is not required
vi app/assets/stylesheets/application.css
/*

+  *= require normalize-rails
 *= require_tree .
 *= require_self
 */
bundle exec rails g scaffold post
bundle exec rake db:migrate
bundle exec rails s

and access to http://localhost:3000/posts and view html source. I can find normalize-rails.css.

  <link rel="stylesheet" media="all" href="/assets/normalize-rails.self-e371c0b120d201389605cb66fa000b511c1fbb27c7ff41142a66fbb0b6165292.css?body=1" data-turbolinks-track="true" />

hirokishirai avatar Aug 17 '16 10:08 hirokishirai

I'm seeing this, only in production environment so @hirokishirai's example doesn't apply. Development environment works fine. Anyone know what is going on here?

ghost avatar Nov 03 '16 01:11 ghost

Out of seemingly nowhere we are seeing this error today. We're seeing locally and in our CI builds.

Rails 5.1.3

Anyone ever figure out what was going on?

mttdffy avatar Jul 02 '18 17:07 mttdffy

Hi @mttdffy, given it's just one file, I ended up just using the asset pipeline to include it in my project like one would any other local CSS file. Probably easier than trying to figure out this error :)

brendon avatar Jul 02 '18 21:07 brendon