chore: adding shopify oxygen example

[joker23]

This PR will add an example application for Shopify Oxygen SDK

---

Note

Adds a Shopify Oxygen SDK example app with build/run setup and registers it in workspaces.

• Example app (packages/sdk/shopify-oxygen/example):
  • Runner: app.ts uses @shopify/mini-oxygen to execute compiled worker and poll fetch output.
  • Example worker: src/index.ts initializes @launchdarkly/shopify-oxygen-sdk, evaluates variation, flushes, and returns { flagKey, flagValue }.
  • Build/Run: package.json scripts (build, start) with tsup and ts-node; includes dependencies and ESM config.
  • Config: adds tsconfig.json and tsup.config.ts for ESM build without externalizing the SDK.
  • Docs: README.md with setup and usage instructions.
• Monorepo config:
  • Adds packages/sdk/shopify-oxygen/example to root package.json workspaces.

^{Written by Cursor Bugbot for commit 5f0d562. This will update automatically on new commits. Configure here.}

[github-actions]

@launchdarkly/browser size report
This is the brotli compressed size of the ESM build.
Compressed size: 169118 bytes
Compressed size limit: 200000
Uncompressed size: 789399 bytes

[github-actions]

@launchdarkly/js-sdk-common size report
This is the brotli compressed size of the ESM build.
Compressed size: 24988 bytes
Compressed size limit: 26000
Uncompressed size: 122411 bytes

[github-actions]

@launchdarkly/js-client-sdk size report
This is the brotli compressed size of the ESM build.
Compressed size: 21981 bytes
Compressed size limit: 25000
Uncompressed size: 75580 bytes

[github-actions]

@launchdarkly/js-client-sdk-common size report
This is the brotli compressed size of the ESM build.
Compressed size: 17636 bytes
Compressed size limit: 20000
Uncompressed size: 90259 bytes

[cursor]

Bug: Example uses latest instead of workspace version

The example package specifies "@launchdarkly/shopify-oxygen-sdk": "latest" which fetches from npm instead of using the local workspace version. Other packages in the monorepo use "*" to reference workspace packages. This causes the example to use a published version rather than the local development version, which breaks the development workflow and could fail if the package isn't published.

 

[joker23]

I think this is fine? If we are only looking at this from a POV of a how-to example, then I'd argue using latest published version is probably more correct.