Feature request

Add example for Fleur.

Fleur is an Flux framework inspired of Fluxible / Redux with modern React API and cool type inference.
It is production ready and working in pixiv Comic with Next.js.

Is your feature request related to a problem? Please describe.

It's not relevant to any problem. This is proposa

Summary

The gatsby-manifest-plugin documentation for generating icons is unclear.

        icon: `src/images/favion.svg`, // This path is relative to the root of the site.
        icons: [
          {
            src: `src/images/favicon--short.svg`,
            sizes: `192x192`,
            type: `image/png`,
         

Since we are now only building Babel on Node.js 14 (even if we still test it on Node.js 6), we can use native ECMAScript modules for the build scripts:

• Top-level scripts
  There are a bunch of scripts/tests in the scripts folder: they can probably all be rewritten to ES modules.
  We can probably add "type": "module" to the top

What pain point are you perceiving?.
I'm reviewing Marked documentation, attempting to create a custom setup where, it transforms new lines starting with 'notice: ' into a specifically formatted DIV. By my understanding I need to first add a custom named tokenizer and then a renderer based on it? Or am I going about this the wrong way?

Describe the solution you'd like
I'd like to ea

Problem

walt-cli package when linking multiple .walt files together can "wrap" the modules in a stand-alone JS module. The resulting module is too large because it serialized the dependency tree with the AST information encoded directly into the output, resulting in a massive amount of js.

Encoding the dependencies into the file is done to ensure the module can be used stand-alone in br

This program doesn't report an error:

type O = { x :: Number, x :: Number }

but it should. The related value has a well-formedness error:

{x : 10, x: 20}

@TimHambourger made a very useful test harness, we could integrate it in our CI somehow (if @TimHambourger is ok with that).

Note we can keep a seperated repo.

Is your feature request related to a problem? Please describe.
Our current CLI commands are too verbose. When it concerns tests, this is annoying. Also, when error occurs, the error message is the only thing I see.

Describe the solution you'd like
I want to run commands silently and, if an error occurs, be able to trace the problem.

Describe alternatives you've considered
I su