v.1.8.1 assets precompile //=require will not be transformed

[forelabs]

Help us help you! Please choose one:

• My app crashes with react-rails, so I've included the stack trace and the exact steps which make it crash.
• My app doesn't crash, but I'm getting unexpected behavior. So, I've described the unexpected behavior and suggested a new behavior.
• I'm trying to use react-rails with another library, but I'm having trouble. I've described my JavaScript management setup (eg, Sprockets, Webpack...), how I'm trying to use this other library, and why it's not working.
• I have another issue to discuss.

---

Hi. We have troubles with the newest release v1.8.1
In our .jsx files we do //= require ./xyz which gets transformed into the code from the required file in development, but not when I ran rake assets:precompile.

We are using sprockets 3.7.0 and I am quite sure that the wrong behaviour is a result of following change:
v1.8.0...v1.8.1#diff-ffad3c61836f28360e5c21dce8362d9fL104 (99eb4e1)

I've locked react-rails to v1.8.0 which resolves the problem, but I don't want to stack to this release.

[rmosolgo]

@seuros Should we revert #574 ?

[seuros]

Let me fix it. I will look into it now.

[seuros]

@forelabs can you provide a sample application ?

[forelabs]

@seuros Sure, here you go: dummy.tar.gz

It requires sprockets 3.7.0 and newest react-rails 1.8.1,
it also has precompiled assets where you can find the not transformed line //= require ...

[rmosolgo]

derp, there it is! hmmm....

[seuros]

@rmosolgo , correct .
I think we should remove that comment from the output.

[forelabs]

@seuros it is not only removing the comment, because this comment should get transformed in the required code because it might be loaded afterwards normally (component gets loaded before requirement because of naming order).

[seuros]

@forelabs The issue is also present in sprocket 4. I will take a look .

[forelabs]

issue will be fixed with #582,
so i close this one here.