coulomb/whynot-design
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

release: @whynot/design v0.4.2 on Forgejo

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06d83-1cbc-71f2-b0dc-e0f48cedae43
This commit is contained in:
tegwick 2026-09-04 23:26:28 +02:00
parent 77cf04eb5e
commit 65247c9320
13 changed files with 88 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

6
BOOTSTRAP.md
View file

@ -19,7 +19,7 @@ ls -la
# .gitea/ .github/ scripts/ tests/
# 3. Replace placeholder host names.
# Search-and-replace `gitea.example.com` with your actual Gitea host in:
# Search-and-replace `forgejo.example.com` with your actual Forgejo host in:
# - package.json
# - .npmrc
# - .gitea/workflows/ci.yml (and .github/ if you keep that)
@ -54,8 +54,8 @@ git push
## Notes
- The `git+ssh` URL in `package.json` (`gitea.example.com/whynot/whynot-design.git`) is a placeholder. Replace with your actual Gitea host.
- The same goes for `.npmrc` and the registry URL in `.gitea/workflows/ci.yml` (commented out — uncomment when you stand up a Gitea Packages registry).
- The `git+ssh` URL in `package.json` (`forgejo.example.com/whynot/whynot-design.git`) is a placeholder. Replace with your actual Forgejo host.
- The same goes for `.npmrc` and the registry URL in `.gitea/workflows/ci.yml` (commented out — uncomment when you stand up a Forgejo Packages registry).
- `.gitea/workflows/ci.yml` and `.github/workflows/ci.yml` are identical. Keep whichever your forge uses and delete the other.
- The `examples/showcase/index.html` page uses `importmap` to load Lit from esm.sh **for the standalone-no-build case**. When you have a bundler in the consuming app, the bundler resolves `lit` from `node_modules` and the importmap is irrelevant.