[No BZ] Set up MiniFlare for local development + external contributors

[roryabraham]

Coming from this old WN post and this comment...

Problem

We don't currently have an obvious setup to test the CSP locally. As a result, we only ever find CSP issues on staging, and at that point they are deploy blockers.

Solution

Open-source the NewDot CSP(s) and set up MiniFlare for local testing.

[melvin-bot[bot]]

Triggered auto assignment to @puneetlath (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details.

[melvin-bot[bot]]

:warning: It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time :warning:

[justinpersaud]

No update yet, working on SMS related issues

[justinpersaud]

Same ☝🏽

[mallenexpensify]

@justinpersaud the BugZero team is adding all E/App issues with the Bug or NewFeature label to a project. This one is kinda lingering. It will surface each week as part of the #expensify-open-source weekly update. Trying to think how best to handle.

1. Add a BZ and add to a project
2. Remove NewFeature
3. Preface title with [No BZ] to denote it's not a normal feature request or bug
4. Something else.

Any thoughts/preferances?

[justinpersaud]

2 or 3 probably work. This is sort of a long standing issue we've had since basically the inception of NewDot. It's something we should do, and nice to do, but I don't know that it takes priority over one of our upcoming releases or waves.

[mallenexpensify]

Thanks @justinpersaud . I'm torn between 2 and 3 but, I imagine there'll be other instances where it makes sense to have NewFeature without it needing a BZ so I'm going to go with #3. I'll update the SO to state

[justinpersaud]

No update

[justinpersaud]

Same

[justinpersaud]

Nothing new here

[roryabraham]

I managed to get a Miniflare instance running and to work around this issue by prepending the command with NODE_EXTRA_CA_CERTS="" like so:

NODE_EXTRA_CA_CERTS="" npx wrangler dev index.js

[justinpersaud]

No update, fire and comp review taking priority

[justinpersaud]

Same

[justinpersaud]

Still the same

[justinpersaud]

Same

[justinpersaud]

Working on #fast-apis issues right now

[justinpersaud]

@roryabraham is this still valuable to do?

[roryabraham]

yep. There have been a number of CSP issues where we've wanted a way to test it locally, and things have not worked when we tested them on staging. here's a semi-recent example.

[roryabraham]

Going to co-assign so it's in my K2 as well, and I can give it a go next time I have a bit of free time.

[justinpersaud]

nothing new yet

[justinpersaud]

Still the same

[justinpersaud]

Ditto

[roryabraham]

no update

[roryabraham]

no update

[justinpersaud]

Still no update

[justinpersaud]

Nothing on my end

[roryabraham]

Headed on parental leave, unassigning. Still think it would be a nice-to-have to make our dev environment more similar to the production environment, but I agree it's not an urgent priority.

[justinpersaud]

Not a priority right now