ayo/mcfly

Back to the Basics. Into the Future. https://mcfly.js.org

Find a file

Ayo 88529ca8d1 feat: registry object		2023-10-07 21:59:10 +02:00
.vscode	initial commit	2023-10-07 20:06:23 +02:00
public	feat: registry object	2023-10-07 21:59:10 +02:00
routes/api/stars/[org]	initial commit	2023-10-07 20:06:23 +02:00
utils	initial commit	2023-10-07 20:06:23 +02:00
.editorconfig	initial commit	2023-10-07 20:06:23 +02:00
.eslintignore	initial commit	2023-10-07 20:06:23 +02:00
.eslintrc	initial commit	2023-10-07 20:06:23 +02:00
.gitignore	initial commit	2023-10-07 20:06:23 +02:00
.npmrc	initial commit	2023-10-07 20:06:23 +02:00
nitro.config.ts	initial commit	2023-10-07 20:06:23 +02:00
package-lock.json	initial commit	2023-10-07 20:06:23 +02:00
package.json	initial commit	2023-10-07 20:06:23 +02:00
README.md	chore: update goals	2023-10-07 20:58:12 +02:00
tsconfig.json	initial commit	2023-10-07 20:06:23 +02:00

README.md

Nitro + Vanilla Custom Elements

This is a minimal Proof of Concept for using Nitro and vanilla JS custom elements using my Web Component Base class.

Setting up

Do the following steps to get you started:

clone project and go into the directory

git clone https://github.com/ayoayco/nitro-web-components.git

cd nitro-web-components

install deps

npm i

run the dev server

npm run dev

open the browser to https://localhost:3000 (or what the dev server said)

Ambitious Goals

These items are not yet achieved in this early POC, but what I have in mind starting this is to find a way to:

create web apps with vanilla custom elements
no frameworks or reactivity libraries on the browser
easy server APIs authoring
server-side pre-rendering
control on when and where JS is downloaded for interactive elements

More info

This project was generated from Nitro starter guide. Look at the Nitro documentation to learn more.