Thanks Jake for shedding some more light on the matter.
That PR is one way to avoid issues, but it's basically the same as
`environment.loaders.delete('nodeModules')` workaround. I thing that more
general and sensible solution would be to simply remove loader by default
and let users define project specific loaders if needed.
Are you currently aware of any package that needs to be tanspiled or is the
loader's purpose to kinda act like a fail safety in case new dependancies
are introduced?
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-core/95bc0d46-d15b-48ab-836a-c7870a4a4f20%40googlegroups.com.
