Back to the Basics. Into the Future. https://mcfly.js.org
Find a file
2023-10-18 21:33:40 +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): spacing 2023-10-16 09:28: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 chore: update content; ignore temp files 2023-10-16 09:26:57 +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 hyper speed 2023-10-18 21:33:40 +02:00
tsconfig.json initial mcfly config and packages 2023-10-12 19:48:50 +02:00

rick_morty_PNG10-min 2

McFly


Back to the Basics.
Into the Future.

McFly is a full-stack no-framework framework that assists developers in leveraging the web platform.

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

Project 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)
  • the idea is, if it is a valid custom element constructor, just throw it in the components directory and it will work... vanilla, Lit, Stencil, or our own totally optional Base Class -- your choice!

Setting up

It's still very early in the project development and we have no packages published yet.

You can, however, experience the framework by cloning the project and play with the example files in the special directories.

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

This framework is a result of an exploration for using Nitro and vanilla JS custom elements using a minimal Web Component Base class.

Nitro is the same production-grade web server powering Nuxt


Just keep building
A project by Ayo Ayco