-
Notifications
You must be signed in to change notification settings - Fork 45
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
ci: switch to npm workspaces setup #670
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
📊 Package size report -0%↓
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
should work just as nice and has a single lockfile for both projects in here. the ui package can afterwards be called from the top-level using e.g. `npm run build --workspace ui`.
df96cd7
to
42be5b7
Compare
@sakulstra there isn't a vercel.json in here, so it is a bit hard to see what should be happening in terms of the UI deployment. wdyt, should we move that into vercel.json? |
3ce7193
to
c251f5f
Compare
I think i don't actually have access to vercel either, @smbdy can you check if this works? |
@sakulstra Should be working fine without |
should work just as nice and has a single lockfile for both projects in here.
the ui package can afterwards be called from the top-level using e.g.
npm run build --workspace ui
.