Back to the Basics. Into the Future. https://mcfly.js.org
Find a file
2023-10-15 01:26:43 +02:00
.vscode initial commit 2023-10-07 20:06:23 +02:00
packages feat: add gh link; rm unused asset 2023-10-15 00:01:51 +02:00
public style(landing-page): apply reset; add spacing 2023-10-15 00:38:00 +02:00
routes feat: initial landing page 2023-10-14 23:52:13 +02:00
src style(landing-page): footer spacing 2023-10-15 01:26:43 +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 test: absolute minimum complexity 2023-10-14 22:26:50 +02:00
.npmrc initial commit 2023-10-07 20:06:23 +02:00
mcfly.config.ts feat: on-route component registry resolution 2023-10-14 23:41:07 +02:00
nitro.config.ts remove deployment config 2023-10-14 10:35:35 +02:00
package-lock.json initial mcfly config and packages 2023-10-12 19:48:50 +02:00
package.json feat: parseScript to get variables 2023-10-10 22:42:43 +02:00
README.md chore: update readme 2023-10-15 01:12:41 +02:00
tsconfig.json initial mcfly config and packages 2023-10-12 19:48:50 +02:00

McFly - Back to the Basics. Into the Future.

McFly is a full-stack web framework that grows with you.

Start at the very basic of writing HTML files and enhance with standard web technologies or go advanced as you like, at your own pace.

It will never get in the way between you and the web platform.

  • HTML pages
  • Server-Side Rendering logic
  • Custom Elements
  • REST APIs
  • Deploy Anywhere

...all in the same project.

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. server-side pre-rendering
  5. control on when and where JS is downloaded for interactive elements

Special directories

1. src/pages

  • file based routing for .html files
  • directly use custom elements (no registry maintenance needed)
  • use <script server:setup> to define logic that runs on the server, which then gets stripped away

2. src/components

  • custom element constructor class files go here (only .js files for now)
  • all components are automatically registered using their file names (e.g., a hello-world.js component can be used as <hello-world> element)

Setting up

Do the following steps to get you started:

  1. clone project and go into the directory
git clone https://github.com/ayoayco/mcfly.git
cd mcfly
  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)

McFly config

To tell McFly you want to use components, pass the mode (only "js" for now) to the components prop mcfly.config.ts

import defineConfig from "./packages/define-config";

export default defineConfig({
  components: "js",
});

More info

At the moment, this is a Proof of Concept and testing ground for using Nitro and vanilla JS custom elements using a minimal Web Component Base class.

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