Skip to content

780 vite update dependencies#794

Open
bourgeoa wants to merge 14 commits into
stagingfrom
780-vite-update-dependencies
Open

780 vite update dependencies#794
bourgeoa wants to merge 14 commits into
stagingfrom
780-vite-update-dependencies

Conversation

@bourgeoa

Copy link
Copy Markdown
Contributor

No description provided.

NoelDeMartin and others added 6 commits June 9, 2026 12:27
- Include staging branch in CI
- Run type checks
- Changed build config from webpack to vite (see details below).
- Moved root files to /lib for better code organization, leaving main entry points in root.
- Implemented custom customElement decorator to work around duplicated registrations.

The new configuration produces the following outputs:

- For npm consumers, *.esm.js and *.cjs.js files. The main export exposes helpers, all components can be registered with solid-ui/components, and individual components can be registered with solid-ui/components/*.
- For modern CDNs, we have ESM bundles in *.js files, also allowing all components or invidiual imports. These now include solid-logic and rdflib, no need to load them separatedly.
- For legacy CDNs, we still have the UMD bundles, but those are discouraged and not documented in the README anymore. These ones still externalize solid-logic and rdflib.

References:
- Lit Publishing docs: https://lit.dev/docs/tools/publishing
- Web Awesome installation docs: https://webawesome.com/docs
- Web Awesome discussion on CDN declarations: shoelace-style/webawesome#2146
@bourgeoa bourgeoa requested a review from NoelDeMartin June 14, 2026 16:46
@bourgeoa bourgeoa assigned bourgeoa and NoelDeMartin and unassigned bourgeoa Jun 14, 2026
@bourgeoa bourgeoa moved this to In review in SolidOS NLNet UI Jun 14, 2026
@bourgeoa bourgeoa moved this from In review to In progress in SolidOS NLNet UI Jun 14, 2026
@bourgeoa bourgeoa removed the request for review from NoelDeMartin June 14, 2026 17:12
- Changed build config from webpack to vite (see details below).
- Moved root files to /lib for better code organization, leaving main entry points in root.
- Implemented custom customElement decorator to work around duplicated registrations.

The new configuration produces the following outputs:

- For npm consumers, *.esm.js and *.cjs.js files. The main export exposes helpers, all components can be registered with solid-ui/components, and individual components can be registered with solid-ui/components/*.
- For modern CDNs, we have ESM bundles in *.js files, also allowing all components or invidiual imports. These now include solid-logic and rdflib, no need to load them separatedly.
- For legacy CDNs, we still have the UMD bundles, but those are discouraged and not documented in the README anymore. These ones still externalize solid-logic and rdflib.

References:
- Lit Publishing docs: https://lit.dev/docs/tools/publishing
- Web Awesome installation docs: https://webawesome.com/docs
- Web Awesome discussion on CDN declarations: shoelace-style/webawesome#2146
#780 Migrate to Vite, Vitest, and Storybook 10
@timea-solid

timea-solid commented Jun 15, 2026

Copy link
Copy Markdown
Member

I am not sure what to make if this PR. It is containing work from other PRs?

@NoelDeMartin

NoelDeMartin commented Jun 15, 2026

Copy link
Copy Markdown
Member

@timea-solid Yes, it was built from my working branch in #787. The commits are displayed as new commits because I rewrote history addressing some feedback before merging the PR. I guess @bourgeoa can cherry-pick his latest commit on top of main now, or reapply the changes, etc. But the last commit in the PR is what we should be looking at. I'll wait until he resolves the conflicts before adding my review though.

@bourgeoa

Copy link
Copy Markdown
Contributor Author

@NoelDeMartin
rebase done
local failing test resolved test/unit/login/login.test.ts
build fails on solid-logic as expected

@NoelDeMartin

Copy link
Copy Markdown
Member

@bourgeoa The rebase didn't work as expected, because you've rebased the branch with my previous commits. If you look at the PR, it says there are 14 new commits but there should only be two (or maybe one, I think I already fixed that test in #796, I guess whichever gets merged first wins xD).

Instead of a rebase, you should cherry-pick or apply your changes from a clean staging checkout. If you have issues doing that let me know and we can jump on a call and I help you do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In progress

Development

Successfully merging this pull request may close these issues.

3 participants