Back to the Basics. Into the Future. https://mcfly.js.org
Find a file
2023-10-07 23:51:40 +02:00
.vscode initial commit 2023-10-07 20:06:23 +02:00
pages feat: nested sub pages 2023-10-07 22:45:45 +02:00
public feat: enable file-based pages 2023-10-07 22:38:35 +02:00
routes feat: use pages directory for custom server assets 2023-10-07 23:51:40 +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 feat: use pages directory for custom server assets 2023-10-07 23:51:40 +02:00
package-lock.json feat: enable file-based pages 2023-10-07 22:38:35 +02:00
package.json feat: use pages directory for custom server assets 2023-10-07 23:51:40 +02:00
README.md chore: update description 2023-10-07 22:27:26 +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

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

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