Back to the Basics. Into the Future. https://mcfly.js.org
Find a file
2023-10-08 04:24:30 +02:00
.vscode initial commit 2023-10-07 20:06:23 +02:00
plugins feat: initial auto insert of registry to head 2023-10-08 02:35:10 +02:00
public feat: generate .output for custom elements 2023-10-08 02:21:20 +02:00
routes feat: initial auto insert of registry to head 2023-10-08 02:35:10 +02:00
src feat: use onChanges hook 2023-10-08 04:24:30 +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 feat: generate .output for custom elements 2023-10-08 02:21:20 +02:00
.npmrc initial commit 2023-10-07 20:06:23 +02:00
nitro.config.ts feat: watch pages and components directory 2023-10-08 04:21:03 +02:00
package-lock.json chore(deps): remove fs 2023-10-08 04:16:54 +02:00
package.json chore(deps): remove fs 2023-10-08 04:16:54 +02:00
README.md chore: update goals 2023-10-08 02:37:14 +02:00
tsconfig.json initial commit 2023-10-07 20:06:23 +02:00

Nitro + Vanilla Custom Elements

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

Setting up

Do the following steps to get you started:

  1. clone project and go into the directory
git clone https://github.com/ayoayco/nitro-web-components.git
cd nitro-web-components
  1. install deps
npm i
  1. run the dev server
npm run dev
  1. open the browser to https://localhost:3000 (or what the dev server said)

Ambitious Goals

We want a way to:

  1. create web apps with vanilla custom elements
  2. write real .HTML files
  3. no frameworks or reactivity libraries on the browser
  4. easy server APIs authoring
  5. server-side pre-rendering
  6. 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.