msw doesn't seem to actually work with this setup about grunge-stack

[eXigentCoder]

Is the issue with Architect running functions in a new process also the reason why I can't seem to get VS Code debugging working with the routes in the Grunge Stack?

Used a debugger; statement in a standard remix app and works like a charm, but in Grunge, no joy 😂

[gnllucena]

any luck trying to make debugger work in grunge stack @eXigentCoder?

[kentcdodds]

Ah, that's a bummer. I tested it in the other stacks but not this one. We may need to be a bit more invasive by requiring the mocks in app code 😬

@tbeseda can you confirm that this will run in a different node process from the app? If so, we may need to move that require into app/entry.server.ts during development.

Would be better if there were a way to do a --require sort of thing with arc directly so we don't have to put it in app code.

[johncantrell97]

Yeah, I'm playing around with running msw in server.ts and it seems to work okay.

[johncantrell97]

Can confirm it does work if you start the server in app/entry.server.ts but it feels like it really slows every request down quite a bit. Also saw some issues with a 3rd party library that was using axios to post.

[tbeseda]

Correct, Architect will run each function execution in a new process. It does use the same environment from the root project/package.json, but doesn't inherit from the parent process. This behavior is important to emulating how Lambda will run the function in isolation on AWS.
Obviously msw is really helpful for mocking APIs that a function would interact with, but I'm not sure how it could be wrapped around a function in Sandbox. A plugin might help, but I think no matter what it has to be started each time a request is made since there are no long running processes.

[pcbl]

I am also facing challenges to debug in grunge stack. Anyonbe knows of some advices to make it work?