npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

julienne

v0.4.3

Published

Small component-driven rendering framework

Downloads

2

Readme

julienne

Small component-driven rendering framework.

Usage

import { createRenderer, createDevRenderer } from 'julienne';

function serverRender(component, props, context) {
  // render component as a string;
  let renderedResult = '...';

  return renderedResult;
}

// Or use createDevRenderer to set up an HMR-enabled dev server.
let renderer = await createRenderer({
  render: {
    client: '/path/to/client/render.js',
    server: serverRender,
  },
  templates: {
    main: require.resolve('./path/to/component.js'),
  },
});

renderer.render('main', propsForMain, context);

API

createRenderer(options) / createDevRenderer(options)

Create a renderer instance.

options.base (optional)

The base public path to serve bundled assets from. See the Vite documentation for more information.

options.cwd (optional)

Set the cwd when compiling and generating the site. It's only necessary to set this when your build script is not in the directory you're generating your site from.

If no value is passed, process.cwd() is used by default.

options.output (optional)

Type:

{
  internal: string;
  public: string;
}

Directories to write the output to. If no output is provided, the following directory structure will be created:

.
├── .julienne
│   ├── client
│   └── server
└── public

public is the directory that the site's bundled application bundle and files will be written to. internal contains files internal to julienne used during rendering.

options.render

Type: object

options.render.client

Type: string

Path to a module that exports a function that renders a component in the browser. The module must export a function as the default export with the following signature:

function render<Component>({
  component,
  props,
  target,
}: {
  component: Component;
  props: Record<string, unknown>;
  target: HTMLElement;
}): void | Promise<void>;
options.render.document (optional)

Function to use to render the document HTML. The function must implement the following signature:

type RenderDocument = (props: {
  body?: string;
  head?: string;
  links?: Attributes[];
  pageData?: unknown;
  scripts?: Attributes[];
}) => string;
options.render.server

Function to use when rendering components on the server. The function must implement the following signature:

type Render<Component> = (
  component: Component,
  props: Record<string, unknown>,
  context?: ServerContext,
) => string | Promise<string>;

options.templates

Type: { [name: string]: string }

An object that maps template names to file paths.

options.viteConfig (optional)

Type: vite.UserConfig

Custom vite configuration.

build(options)

Compiles and writes the application's bundle to the public output directory.

Example usage:

import { build } from 'julienne';
await builder.build(options);

options.base (optional)

The base public path to serve bundled assets from. See the Vite documentation for more information.

options.cwd (optional)

Set the cwd when compiling and generating the site. It's only necessary to set this when your build script is not in the directory you're generating your site from.

If no value is passed, process.cwd() is used by default.

options.output (optional)

Type:

{
  internal: string;
  public: string;
}

Directories to write the output to. If no output is provided, the following directory structure will be created:

.
├── .julienne
│   ├── client
│   └── server
└── public

public is the directory that the site's bundled application bundle and files will be written to. internal contains files internal to julienne used during rendering.

options.render

Type: object

options.render.client

Type: string

Path to a module that exports a function that renders a component in the browser. The module must export a function as the default export with the following signature:

function render<Component>({
  component,
  props,
  target,
}: {
  component: Component;
  props: Record<string, unknown>;
  target: HTMLElement;
}): void | Promise<void>;

options.templates

Type: { [name: string]: string }

An object that maps template names to file paths.

options.viteConfig (optional)

Type: vite.UserConfig

Custom vite configuration.

License

MIT