feat(buyers): document guest buyer

[gryevns]

Description

TA-7931

Adds documentation for buyer prop.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own changes
• I have run yarn lint to make sure my changes pass all tests
• I have run yarn test to make sure my changes pass all linters
• I have pulled the latest changes from the upstream main branch
• I have tested both the react and the CDN versions on local and integration environments
• I have added the necessary labels to this PR in case a new release needs to be published after merging into main (e.g. release and patch)

Contribution guidelines

For contribution guidelines, styleguide, and other helpful information please
see the CONTRIBUTING.md file in the root of this project.

[luca-gr4vy]

You can probably add those two vulnerability codes to .trivignore for now

[gryevns]

You can probably add those two vulnerability codes to .trivignore for now

I think they should probably be fixed to meet security requirements. I tried creating a PR for axios but another one just popped up...

[luca-gr4vy]

You can probably add those two vulnerability codes to .trivignore for now

I think they should probably be fixed to meet security requirements. I tried creating a PR for axios but another one just popped up...

Usually we try to fix it by upgrading the dependency itself or any parent ones, although that might be hard. Sometimes it's enough to just resolve to the fixed version using yarn resolutions (we do that too). Not sure if this would solve it:

// package.json
resolutions: {
  ...
  "axios": "^1.7.4",
  "minimatch": "^4.0.8"
}

(then run yarn and commit the updated yarn.lock)

[gryevns]

You can probably add those two vulnerability codes to .trivignore for now

I think they should probably be fixed to meet security requirements. I tried creating a PR for axios but another one just popped up...

Usually we try to fix it by upgrading the dependency itself or any parent ones, although that might be hard. Sometimes it's enough to just resolve to the fixed version using yarn resolutions (we do that too). Not sure if this would solve it:

// package.json
resolutions: {
  ...
  "axios": "^1.7.4",
  "minimatch": "^4.0.8"
}

(then run yarn and commit the updated yarn.lock)

I had a quick look but couldn't get webpack to update. There are lots of upgrades based on the PRs open for this repo - perhaps they need to be tackled first.

[luca-gr4vy]

@gryevns this should help #217

[gr4vy-code]

🚀 PR was released in v2.29.0 🚀