why did we use the minispade string strategy for development?
This commit is contained in:
parent
818a91e1e5
commit
10b19b64b1
|
@ -49,7 +49,9 @@ input assets.scripts do
|
||||||
|
|
||||||
match %r(^(?!vendor|spec).*\.js$) do
|
match %r(^(?!vendor|spec).*\.js$) do
|
||||||
modules = proc { |input| input.path.gsub(%r((^app/|lib/|\.js$)), '') }
|
modules = proc { |input| input.path.gsub(%r((^app/|lib/|\.js$)), '') }
|
||||||
minispade(string: assets.development?, rewrite_requires: true, module_id_generator: modules)
|
# why did we use the string strategy for development? makes it impossible to set breakpoints
|
||||||
|
# minispade(string: assets.development?, rewrite_requires: true, module_id_generator: modules)
|
||||||
|
minispade(string: false, rewrite_requires: true, module_id_generator: modules)
|
||||||
end
|
end
|
||||||
|
|
||||||
match %r(^(?!spec).*\.js$) do
|
match %r(^(?!spec).*\.js$) do
|
||||||
|
|
Loading…
Reference in New Issue
Block a user