mcfly/packages/core
2025-01-14 20:35:57 +01:00
..
cli feat: remove manual copy during build cmd 2025-01-14 18:40:22 +01:00
runtime refactor: add getNitroConfig for consolidating different nitro config sources 2025-01-10 17:23:31 +01:00
test feat: move cli to core (#55) 2025-01-08 21:21:31 +01:00
get-nitro-config.js refactor(core): use nitro runtimeConfig to pass mcfly config file path 2025-01-14 01:01:00 +01:00
LICENSE chore(packages): update LICENSEs 2023-11-09 11:33:02 +01:00
mcfly-nitro-config.js refactor: add getNitroConfig for consolidating different nitro config sources 2025-01-10 17:23:31 +01:00
package.json fix(core): use c12 to load mcfly config from route middleware 2025-01-10 17:43:25 +01:00
README.md chore: use small logo 2025-01-09 17:39:29 +01:00
route-middleware.js refactor: remove relativePath processing 2025-01-14 20:35:57 +01:00
vitest.config.mjs feat: move cli to core (#55) 2025-01-08 21:21:31 +01:00

rRick & Morty cartoon

McFly

McFly is a no-framework metaframework
that assists in leveraging the web platform

Why

I often wonder what it would look like to build sites & apps knowing just the basics.

I thought:

McFly is my reimagination of web development: Back to the basics. Into the future.

Project Status

We are currently in a Proof of Concept phase. All parts are subject to breaking changes in minor releases.

Try it today

Run the following to generate a McFly starter project.

npm create mcfly@latest

Features

Use vanilla custom elements (or sugar-coated web components)
Write server-powered .html pages
"Use the Platform™" on both server runtimes & browsers
Use server-side rendering
Deploy anywhere, even the Edge

Special directories

1. ./src/pages/

  • file-based routing for .html files
  • directly use custom elements & static fragments (no imports or 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 files (only .js files for now)
  • all components are automatically registered using their file names; a hello-world.js component can be used as <hello-world>
  • static .html fragments; a my-header.html fragment can be directly used as <my-header>

3. ./src/api/

  • file-based routing for REST API endpoints
  • e.g., ./src/api/users.ts can be accessed via http://<domain>/api/users
  • TypeScript or JavaScript welcome!

Packages

The following are the project packages published on the NPM registry:

Package Description Version
@mcflyjs/cli The McFly CLI tooling npm version
@mcflyjs/config Nitro server config for McFly projects npm version
@mcflyjs/core Route event and config handlers npm version
create-mcfly Script for scaffolding a new McFly workspace npm version

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