Skip to content

feat(website-server): Install repomix from GitHub main branch #1055

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yamadashy merged 2 commits into from
Dec 31, 2025
+36 −39
Merged

feat(website-server): Install repomix from GitHub main branch #1055

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
59b498b
feat(website-server): Install repomix from GitHub main branch
yamadashy Dec 31, 2025
1f058ef
fix(website-server): Add git to Docker build stages and update lock file
yamadashy Dec 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion website/server/Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,9 @@
# ==============================================================================
FROM node:24-alpine AS builder

# Install git (required for GitHub-based npm dependencies)
RUN apk add --no-cache git

WORKDIR /app
COPY package*.json ./

Expand All @@ -20,11 +23,14 @@ RUN npm run build
# ==============================================================================
FROM node:24-alpine AS deps

# Install git (required for GitHub-based npm dependencies)
RUN apk add --no-cache git

WORKDIR /app
COPY package*.json ./

# Install only production dependencies
RUN npm ci --only=production --ignore-scripts && \
RUN npm ci --omit=dev --ignore-scripts && \
npm cache clean --force

# ==============================================================================
Expand Down
65 changes: 28 additions & 37 deletions website/server/package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion website/server/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
"@hono/node-server": "^1.19.7",
"fflate": "^0.8.2",
"hono": "^4.11.1",
"repomix": "^1.11.0",
"repomix": "github:yamadashy/repomix#main",
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Dec 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Pinning a dependency to a Git branch like main is useful for integrating the latest changes quickly. However, this can introduce instability, as the main branch may contain work-in-progress or breaking changes. An npm update could pull in these changes unexpectedly.

For greater stability and more predictable dependency updates, consider pinning to a specific commit hash instead. This ensures that you are always building against a known, fixed version of the code.

Example:

"repomix": "github:yamadashy/repomix#<specific-commit-hash>"

This would require manually updating the commit hash in package.json when you want to pull in new changes, making the update process more explicit. Given the context of testing the latest features, your current approach is understandable, but this is a common practice for ensuring build reproducibility.

"winston": "^3.19.0",
"zod": "^4.2.1"
},
Expand Down
Loading