-
Notifications
You must be signed in to change notification settings - Fork 9
fix: harden cookie flags, sanitize Genie markdown output, fix remote tunnel #216
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.
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,7 +10,7 @@ | |
| "build": "npm run build:app", | ||
| "build:app": "tsdown --out-dir build server/index.ts && cd client && npm run build", | ||
| "build:server": "tsdown --out-dir build server/index.ts", | ||
| "install": "cd client && npm ci && cd ..", | ||
| "install": "cd client && npm install && cd ..", | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. CC @MarioCadenas we need to revert that, otherwise the
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. so? npm ci sould work anyway, what's the problem with that?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nope, because the lock file doesn't match - when pnpm
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. are we running this one on ci at any moment? or just locally?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. no, only locally |
||
| "preview": "vite preview", | ||
| "check": "tsc", | ||
| "clean": "rm -rf build && cd client && rm -rf dist", | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -27,5 +27,12 @@ export default defineConfig([ | |
| return /^[^./]/.test(id) || id.includes("/node_modules/"); | ||
| }, | ||
| tsconfig: "./tsconfig.json", | ||
| copy: [ | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This was needed to resolve an issue that crashed the app when running the tunnel: |
||
| { | ||
| from: "src/plugins/server/remote-tunnel/*.html", | ||
| to: "dist/plugins/server/remote-tunnel", | ||
| flatten: true, | ||
| }, | ||
| ], | ||
| }, | ||
| ]); | ||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
prepare-pr-template.tsrewrites dependencies to file: tarballs, which will never match the lockfile copied from template - so we need to revert thisThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
true, but I guess now we have fixed deps it should be fine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No - see this failure: https://github.com/databricks/appkit/actions/runs/23590462691/job/68694129912
The prepare-pr-template.ts script rewrites deps from registry specifiers to file paths. The lockfile still references the original registry URLs, so npm ci will fail because the specifiers don't match - regardless of whether versions are pinned.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant keeping npm install sorry, I understand we can't keep npm ci in there