coffee-rails-source-maps 1.2.2 → 1.2.3
Sign up to get free protection for your applications and to get access to all the features.
- data/README.md +0 -8
- data/lib/coffee-rails-source-maps.rb +1 -1
- data/lib/coffee-rails-source-maps/version.rb +1 -1
- metadata +3 -3
data/README.md
CHANGED
@@ -44,14 +44,6 @@ Finally to see your CoffeeScript code in the Chrome console just add a `debugger
|
|
44
44
|
|
45
45
|
Ah, yes, I too have run into this. If you're using the asset-pipeline, and you probably are since this gem requires it. Then you need to touch your CoffeeScript files in order for the asset-pipeline to generate the map for that file. Once you do that the next time you access the file in Chrome a source map should be generated for you and you'll see it in the browser.
|
46
46
|
|
47
|
-
If you're still not seeing source maps trying adding:
|
48
|
-
|
49
|
-
```ruby
|
50
|
-
gem 'tilt'
|
51
|
-
```
|
52
|
-
|
53
|
-
in your `Gemfile` before the `coffee-rails-source-maps` gem. That has been proven to fix the issue.
|
54
|
-
|
55
47
|
Good luck!
|
56
48
|
|
57
49
|
## Acknowledgements
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: coffee-rails-source-maps
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.2.
|
4
|
+
version: 1.2.3
|
5
5
|
prerelease:
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -74,7 +74,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
|
|
74
74
|
version: '0'
|
75
75
|
segments:
|
76
76
|
- 0
|
77
|
-
hash:
|
77
|
+
hash: -1186147679494053002
|
78
78
|
required_rubygems_version: !ruby/object:Gem::Requirement
|
79
79
|
none: false
|
80
80
|
requirements:
|
@@ -83,7 +83,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
83
83
|
version: '0'
|
84
84
|
segments:
|
85
85
|
- 0
|
86
|
-
hash:
|
86
|
+
hash: -1186147679494053002
|
87
87
|
requirements: []
|
88
88
|
rubyforge_project:
|
89
89
|
rubygems_version: 1.8.25
|