-
Notifications
You must be signed in to change notification settings - Fork 10
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
chore: tidy-up scripts #2024
chore: tidy-up scripts #2024
Conversation
🔭🐙🐈 Test this branch here: https://db-ui.github.io/mono/review/chore-tidy-up-scripts |
# Conflicts: # .github/workflows/02-e2e-showcases.yml # .github/workflows/02-e2e.yml # e2e/Dockerfile # e2e/package-lock.json # e2e/package.json # package-lock.json
# Conflicts: # .github/workflows/02-e2e-showcases.yml
@nmerget I'm still struggling with "just" moving our scripts to a sub-package. Out of npm/rfcs#190 I found https://github.com/google/wireit – what do you think about that for some consolidation ? To me this solution seems to be simpler than |
We can check out https://github.com/google/wireit. But I would recommend doing it in another branch. |
…e-tidy-up-scripts # Conflicts: # package-lock.json
Proposed changes
Moved some
scripts
from rootpackage.json
toscripts/package.json
to have a better overview.Most of the scripts are needed because of npm-run-all, as we can't run scripts in parallel on npm workspaces yet.
closes #1541
closes #1958
Types of changes
Further comments