`bin/rake webpacker:compile` fails with angular example about webpacker

[taboularasa]

@gauravtiwari thanks for following up. I just tested the repo steps on a new rails project and can confirm that this is no longer an issue

[joerodrig]

It looks like this is being caused by the require statement in the hello_angular.js file that's being generated at line 7. I was able to get the app to compile by moving the require statement to application.js and changing it to an import statement.
ie. import HelloAngular from "./hello_angular". You can see in the React example, the file loads a component, whereas this one seems to be requiring itself.

[taboularasa]

@joerodrig3 thanks for taking some time to look at this! Thats a good observation you made about hello_angular.js:7 requiring itself, I don't understand what the intention is there. I was able to reproduce your suggested fix by removing the require to application.js that does allow bin/rake webpacker:compile to succeed but that's also just a noop, the app is never actually booted. application.js is then requiring an empty file. The other curious detail is the app does successfully run locally without any modification via bin/webpack-watcher

I think I'll look at some other Angular 2 / webpack examples and see how it's being done there.

[mikerob215]

Ran into this issue in a work project with our own webpack integration. The issue is that when you use ts-loader, and compile using webpack --json, the output will contain that string that caused the error in the op and then the JSON that the webpack:compile rake task is looking for. I've had this also happen with awesome-typescript-loader, I'm not sure what other loaders could cause this. I've submitted a pr that will cause the rake task to ignore any string that precedes the JSON it is looking for. #85

[gauravtiwari]

Does this work now @taboularasa? There has been some updates lately, which I think fixes this problem. Please close this issue if it does :)

[gauravtiwari]

Awesome 🎉 Have some 🍰