aholthagerty
aholthagerty
I ran into this, as well. (backend on same origin as frontend, but still no sentry-trace header sent). I updated `tracingOrigins` to include a regex for any relative url, and...
I couldn't find any mention of this within the migration guide, but it appears `` was renamed to `` in v6.
Well this is frustrating. I am getting this same error and have no clue what to do about it. using `npx nx g @nx/node:application --dry-run`
Was able to fix it locally for me by editing `node_modules/@nx/jest/src/plugins/plugin.js` line 12 to be: `const package_json_workspaces_1 = require("nx/plugins/package-json-workspaces");` definitely a hacky solution, though. it appears `@nx/jest` is looking in...
going to comment here to keep this issue from auto-closing.
I am having this issue currently and it is beyond frustrating. System setup: Windows 10, running in WSL 2.0 Ubuntu. Have also tried running within the node:20-alpine Docker image and...
> This is effectively the same thing as running just the serve command for production. > cc: @aholthagerty this should address your issue as well. I ran into this while...
> Looks good. Would it be possible to write an integration test for this? Added!
Anything that needs to be done to get this merged? I have other team mates that have been affected by this bug.
Pinging again. This bug still affects us, and this PR would fix it.