riot-4-fun v0.2.1

riot-4-fun

Let's play riot 4+, FOR FUN.

It is JUST for fun.

I try to have a HTTP server solution for my only need, so there is no much wise choice or best practice.
Everything recalls a simple concept - easy using and fun for developer.

This project uses

• HTML, Js, CSS
• node.js and npm
• Riot
• Sass
• esbuild

Features

• Multiple components in one single file.
• Support Store/Context.
• One Js file to configure everything.
• Server side rendering (SSR).
• Can import from npm packages.
• Bundle files by page.

Multiple components in one single file

For eaiser code arrangement, we want to tear the whole component as several parts. For example a complex li in ul. But we clearly know that all parts work together and won't needed for any others, it is really unnecessary to have another files for these parts. So we can simply write code as followed:

<part1>
  This is custom component 1.
</part1>

<part2>
  This is custom component 2.
  <script>
    export default {
      components: { part1 }
    };
  </script>
</part2>

<final>
  <part1/>
  <part2/>
  This is the component which will be exported as the default.

  <script>
    export default {
      components: { part1, part2 }
    };
  </script>
</final>

Be awared that the last compnent in the file will be the real export default component after compiling.

Support Store/Context.

For easier handling datas as context/store acrossing components, here provide a simple <store> component which bases on riot plugin.

<component>
  Let's try "store" - {count}.
  <store name='SAMPLE_STORE' listener={SampleStoreListen}/>
  <script>
    import store from 'riot-4-fun/SRC/Store.riot';

    export default {
      components: { store },
      state: {
        count: 0
      },
      SampleStoreListen (store, params) {
        const { count } = store;

        this.update({ count });
      }
    };
  </script>
</component>

One Js file to configure everything.

riot-4-fun needs only one Js file to configure route, resource, page, and everything.

import Http from 'riot-4-fun/SRC/Http.js';
import homePage from './src/lib/homePage.js';
import signIn from './src/lib/signin.js';

const R4F = { // riot-4-fun config.
  port: 3000,
  page: {
    '/home': {
      title: '',
      description: '',
      keywords: '',
      author: '',
      favicon: '',
      feed: '',
      css: [ '/style.css' ],
      js: [ '/library.js' ],
      body: {
        type: 'riot',
        component: './src/components/home.riot',
        Initialize: homePage,
      }
    },
    '/page1': {
      body: {
        type: 'riot',
        component: './src/components/page1.riot'
      }
    }
  },
  errorPage: {
    '404': {
      ...DftPgRt,
      title: '404',
      body: { type: 'riot', component: './src/components/error404.riot' }
    },
    '500': {
      title: '500',
      body: { type: 'riot', component: './SRC/components/error500.riot' }
    }
  },
  service: {
    '/signin': {
      post: signIn
    }
  },
  route: [
    {
      path: 'favicon.ico',
      type: 'resource',
      location: './public'
    }
  ]
};

Http.Build(R4F, 'mjs').Initialize(R4F).Run();