Insight as to why this might not work with Heroku deployment?

npm run build successfully appends the file when I run it locally but not when Heroku runs it during deployment. I can see that it’s running the script in the deploy logs but when I view the file in build it doesn’t have the appended code.

=====> Detected Framework: React.js (create-react-app)
       Using existing `static.json`
       Enabling runtime environment variables
> react-app@0.1.0 build /tmp/build_...
> npm run build-css && react-scripts build && cra-append-sw ./custom-sw.js

Thanks for making this workaround!

[bplittle]

Update: When I use the --skip-compile flag it works as expected!

So just to summarize, without the flag npm run build works fine locally, but not when deployed via Heroku (babel-loader error seen in the build logs above occurs and the file is not appended).

Thanks for your tool!

[temitope]

FWIW i am getting a similar issue when trying to build. Isolated the same behavior by running it directly from the bin folder in node_module install folder. Calling it directly on the custom-sw.js i created. ----Output—

(node:90864) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Hash: c68b1d1fde198868d1dc
Version: webpack 4.27.1
Time: 60ms
Built at: 2018-12-14 13:47:29
    Asset   Size  Chunks             Chunk Names
bundle.js  4 KiB    main  [emitted]  main
Entrypoint main = bundle.js
[0] multi ./src/custom-service-worker.js 28 bytes {main} [built]

ERROR in multi ./src/custom-service-worker.js
Module not found: Error: Can't resolve 'babel-loader' in '/Users/username/web-app'