Steve Pavlin

Hi @mars Thanks for your message. This is what I've tried: ``` import runtimeEnv from '@mars/heroku-js-runtime-env'; class App extends Component { render() { // Load the env object. const env...

Hi @mars , thanks for the support. The issue was actually having a cache control header on javascript resources in `static.json`: ``` "**.js": { "Cache-Control": "public, max-age=31536000" } ``` If...

This is my static.json: ``` { "root": "build/", "routes": { "/**": "index.html" }, "headers": { "/": { "Cache-Control": "no-store, no-cache" }, "**.js": { "Cache-Control": "public, max-age=31536000" }, "**.css": { "Cache-Control":...

Can confirm this is most likely a windows bug in either code-coverage or instrument-cra causing the file-based coverage to display incorrectly, aggregate coverage is being reported correctly in our CI...

For anyone else interested in solving this problem with this style of architecture. The way to transactionally ensure an email gets sent after a business transaction is the [outbox pattern](https://jimmybogard.com/life-beyond-distributed-transactions-an-apostates-implementation-relational-resources/)....

Was getting this as well, seems to be fixed after restarting the dev server when setting REACT_APP_UA_ID in the env 👍

I began to do some work on this and found all the v1.8.3 NMS methods that were used in the last developed version. I created a gist of the class...

No I haven't, it seems like it was still included in the pet AI in version 1.8 R1 all I have done was scan the NMS 1.8.3 classes that were...