Back to the Basics. Into the Future.
https://mcfly.js.org
| .vscode | ||
| plugins | ||
| public | ||
| routes | ||
| src | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .npmrc | ||
| nitro.config.ts | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
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:
- 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)
Special directories
src/pages
- file based routing for
.htmlfiles
src/components
- custom element constructor class files go here (only
.jsfiles for now) - all components are automatically registered using their file names (e.g., a
hello-world.jscomponent can be used as<hello-world>element)
Ambitious Goals
We want a way to:
- create web apps with vanilla custom elements
- write real .HTML files
- 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.