run-llama/create-llama
1
0
Fork 0
mirror of https://github.com/run-llama/create-llama.git synced 2026-07-15 13:15:42 -04:00
Code Issues 39 Packages Projects Releases 10 Wiki Activity

[PR #678] [MERGED] fix: conflict package versions in ts examples #680

New Issue
Closed
opened 2026-02-15 20:15:50 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 20:15:50 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/run-llama/create-llama/pull/678
Author: @thucpn
Created: 6/4/2025
Status: ✅ Merged
Merged: 6/4/2025
Merged by: @marcusschiesser

Base: main ← Head: tp/fix-conflict-package-versions-in-ts-examples

📝 Commits (5)

  • 25d635f fix: conflict package versions in ts examples
  • 7a4e92d use single instance of @llamaindex/workflow
  • 5d18a7a fix imports when bumping openai
  • 0aab544 clean code
  • c6bedf0 missing Settings.llm

📊 Changes

6 files changed (+511 additions, -189 deletions)

View changed files

📝 packages/server/examples/agentic-rag/index.ts (+2 -7)
📝 packages/server/examples/custom-layout/index.ts (+6 -1)
📝 packages/server/examples/devmode/index.ts (+6 -0)
📝 packages/server/examples/package.json (+5 -6)
📝 packages/server/examples/simple-workflow/calculator.ts (+6 -1)
📝 pnpm-lock.yaml (+486 -174)

📄 Description

Duplicate Dependency Resolution Issue:
The examples package explicitly listed @llamaindex/workflow@1.1.3 in its dependencies, while @llamaindex/server@workspace:* (linked to packages/server) also depended on @llamaindex/workflow@1.1.3. pnpm resolved these as separate instances of @llama-flow/core@0.4.1 and causing an instanceof mismatch

To detect issue: cd packages\server\examples && pnpm why @llama-flow/core

@llamaindex/server link:..
└─┬ @llamaindex/workflow 1.1.3
  └── @llama-flow/core 0.4.1
  
@llamaindex/workflow 1.1.3
└── @llama-flow/core 0.4.1

llamaindex 0.11.1
└─┬ @llamaindex/cloud 4.0.9
  └── @llama-flow/core 0.4.1 peer

This PR is to remove @llamaindex/workflow from the examples package’s dependencies and rely on @llamaindex/server to provide it. This ensures a single instance of @llama-flow/core@0.4.1 is used in examples and server.

Summary by CodeRabbit

  • Chores
    • Updated dependency versions for improved compatibility and stability.
    • Removed an unused workflow dependency.
  • Refactor
    • Adjusted import sources for AI-related classes to enhance clarity and maintainability.
    • Explicitly configured the language model used in workflows and server setups.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/run-llama/create-llama/pull/678 **Author:** [@thucpn](https://github.com/thucpn) **Created:** 6/4/2025 **Status:** ✅ Merged **Merged:** 6/4/2025 **Merged by:** [@marcusschiesser](https://github.com/marcusschiesser) **Base:** `main` ← **Head:** `tp/fix-conflict-package-versions-in-ts-examples` --- ### 📝 Commits (5) - [`25d635f`](https://github.com/run-llama/create-llama/commit/25d635f626216e5b07bd11daed5f75e634d16968) fix: conflict package versions in ts examples - [`7a4e92d`](https://github.com/run-llama/create-llama/commit/7a4e92d7b7bff17566ada8a65d3cd27fa5f053a9) use single instance of @llamaindex/workflow - [`5d18a7a`](https://github.com/run-llama/create-llama/commit/5d18a7ac9706874a243d04195792399b0e3d138c) fix imports when bumping openai - [`0aab544`](https://github.com/run-llama/create-llama/commit/0aab5449636b66348665dc654b4d24c832808fff) clean code - [`c6bedf0`](https://github.com/run-llama/create-llama/commit/c6bedf07f8bf1786db04d98a384b88fac6e1a161) missing Settings.llm ### 📊 Changes **6 files changed** (+511 additions, -189 deletions) <details> <summary>View changed files</summary> 📝 `packages/server/examples/agentic-rag/index.ts` (+2 -7) 📝 `packages/server/examples/custom-layout/index.ts` (+6 -1) 📝 `packages/server/examples/devmode/index.ts` (+6 -0) 📝 `packages/server/examples/package.json` (+5 -6) 📝 `packages/server/examples/simple-workflow/calculator.ts` (+6 -1) 📝 `pnpm-lock.yaml` (+486 -174) </details> ### 📄 Description **Duplicate Dependency Resolution Issue:** The examples package explicitly listed @llamaindex/workflow@1.1.3 in its dependencies, while @llamaindex/server@workspace:* (linked to packages/server) also depended on @llamaindex/workflow@1.1.3. pnpm resolved these as separate instances of @llama-flow/core@0.4.1 and causing an **instanceof** mismatch To detect issue: `cd packages\server\examples && pnpm why @llama-flow/core` ``` @llamaindex/server link:.. └─┬ @llamaindex/workflow 1.1.3 └── @llama-flow/core 0.4.1 @llamaindex/workflow 1.1.3 └── @llama-flow/core 0.4.1 llamaindex 0.11.1 └─┬ @llamaindex/cloud 4.0.9 └── @llama-flow/core 0.4.1 peer ``` This PR is to remove @llamaindex/workflow from the examples package’s dependencies and rely on @llamaindex/server to provide it. This ensures a single instance of @llama-flow/core@0.4.1 is used in examples and server. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Chores** - Updated dependency versions for improved compatibility and stability. - Removed an unused workflow dependency. - **Refactor** - Adjusted import sources for AI-related classes to enhance clarity and maintainability. - Explicitly configured the language model used in workflows and server setups. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-15 20:15:50 -05:00
yindo closed this issue 2026-02-15 20:15:50 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/create-llama#680
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?