chore: update package-lock.json and tsconfig.json

[bevy-automate]

Review PR opened from #5

Summary by CodeRabbit

• Chores
  • Updated TypeScript compiler configuration settings to optimize module resolution behavior.

Note: This release contains only build configuration updates with no visible end-user changes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7964b204-f79a-46e6-8c27-401cc2159881

📥 Commits

Reviewing files that changed from the base of the PR and between c02fa23 and b1d7cf8.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• tsconfig.json

📜 Recent review details

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: CR
Repo: bevycommerce/mock-bridge PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-24T22:08:51.852Z
Learning: Applies to src/**/*.ts : TypeScript code must be built using `npm run build` before execution

📚 Learning: 2026-03-24T22:08:51.852Z

Learnt from: CR
Repo: bevycommerce/mock-bridge PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-24T22:08:51.852Z
Learning: Applies to src/**/*.ts : TypeScript code must be built using `npm run build` before execution

Applied to files:

• tsconfig.json

🔇 Additional comments (2)

tsconfig.json (2)

16-16: Downgrading moduleResolution from node16 to node loses modern resolution features.

The node16 resolution properly supports package.json exports fields, which is standard for modern packages. Switching to legacy node resolution may cause issues with packages that rely on exports for proper module/type exposure.

If this change is to work around Shopify package type resolution issues, consider keeping node16 and using types/typeRoots or checking if the Shopify packages have documented TypeScript configuration requirements.

[raise_major_issue, request_verification]

`@shopify/shopify-app-react-router` TypeScript configuration moduleResolution

---

18-25: Path mappings point to internal package distribution paths—these are fragile and may break on updates.

The paths reference internal dist/ts/ locations:

• ./node_modules/@shopify/shopify-app-react-router/dist/ts/server/index.d.ts
• ./node_modules/@shopify/shopify-api/dist/ts/adapters/web-api/index.d.ts

These internal paths are implementation details, not part of the packages' public API. They could change in minor or patch releases without warning.

Additionally, paths only affects TypeScript compilation—Node.js resolves modules differently at runtime using the package's actual exports. If the .d.ts types don't precisely match the runtime exports, you may encounter type/runtime mismatches that won't surface until runtime.

[raise_major_issue, request_verification]

Run the following to verify the packages' export structure and check if these internal paths exist:

#!/bin/bash
# Check if the targeted .d.ts files exist and inspect package exports

echo "=== Checking `@shopify/shopify-app-react-router` ==="
cat node_modules/@shopify/shopify-app-react-router/package.json | jq '.exports, .types, .typings' 2>/dev/null || echo "Package not found or no exports field"

echo ""
echo "=== Checking `@shopify/shopify-api` ==="
cat node_modules/@shopify/shopify-api/package.json | jq '.exports, .types, .typings' 2>/dev/null || echo "Package not found or no exports field"

echo ""
echo "=== Verifying targeted .d.ts paths exist ==="
ls -la node_modules/@shopify/shopify-app-react-router/dist/ts/server/index.d.ts 2>/dev/null || echo "Path NOT found: dist/ts/server/index.d.ts"
ls -la node_modules/@shopify/shopify-api/dist/ts/adapters/web-api/index.d.ts 2>/dev/null || echo "Path NOT found: dist/ts/adapters/web-api/index.d.ts"

---

Walkthrough

TypeScript configuration updated to change module resolution strategy from "node16" to "node", and path mappings added to direct compilation of two Shopify packages to specific declaration files within node_modules.

Changes

Cohort / File(s)	Summary
TypeScript Configuration tsconfig.json	Updated moduleResolution from "node16" to "node", added baseUrl: ".", and introduced paths mappings for two Shopify packages to force compile-time resolution to specific .d.ts declaration files.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title mentions updating both package-lock.json and tsconfig.json, but the raw summary shows only tsconfig.json was modified with TypeScript module resolution changes.	Update the title to reflect the actual changes: 'chore: update tsconfig.json module resolution' or verify if package-lock.json changes are included in the full changeset.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/react-router-admin-auth

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.