-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wildcard asset notation no longer works? #45
Comments
Hello @Vernadsky, Could you check it with other versions of this gem and specify version which works well with your assets? Please specify versions which cannot process your assets correctly. |
Hi @bdrazhzhov, Version 0.6.2.2 works fine (I've tried that version by manually specifying the 'v0.6.2.2' tag in my gemfile), the problem was introduced in 0.6.2.3. I suspect commit 0965b68 breaks it. |
Can you please try
|
Unfortunately that version doesn't work either. |
Do you have a reason for not using the already included by default path Alternatively you can try add your custom path like this:
I'm no expert in the asset pipeline but to my knowledge you put the custom paths in |
I've moved the app/assets/javascripts/lib files lib/assets/javascripts, but that doesn't solve the issue. Wildcards still don't work (neither versions). |
I'm having the same issue. Any idea guys? |
@Zyphrax and/or @Vernadsky, please provide replication steps, or even better, a test project. |
I've noticed that this error only occurs when I use the .ts extension, it all works fine if I name my files .js.ts. |
I've just upgraded to the latest version of typescript-rails, and now I get the following error:
It works if I specify
dashboard.js
directly inassets.rb
(the file is actuallydashboard.ts
).But normally wildcards work fine:
I've tried variations with
.ts
instead of.js
.Did one of the commits break wildcard support?
The text was updated successfully, but these errors were encountered: