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

notion-viewer-client

v0.0.5

Published

A simple and easy to use package for rendering notion pages in your application.

Downloads

12

Readme

Notion Viewer Client

  • A simple and easy to use package for rendering notion pages in your laravel application.
  • This package also offers you a renderer out of the box. You can use it to render your notion pages on your own.
  • You can add or remove the default renderers and use your own renderer too.

Table of Contents

How it works

Since notion api doesn't support CORS and don't recommend making API calls from a webpage (see here), you may need to install laravel-notion-viewer composer package in order to get notion blocks from Notion Api.

But you can also use your own server to get the blocks from Notion Api and pass the blocks to the Renderer class in your client.


Installation

Install via npm

npm install notion-viewer-client

Usage

  • NotionViewer

NotionViewer.render(id: string, element: HTMLElement, endPoint?: string)

Using axios, XHR request will be sent to endPoint to get the blocks from Notion Api and then render the blocks in element.

By default, the endPoint is /laravel-notion-viewer/data/{id} which is a route offered by laravel-notion-viewer.

You can specify your own endpoint to get the blocks from your own server.

Example Usage:

import NotionViewer from 'notion-viewer-client';

let notionPageId = 'this-is-a-notion-page-id'; // If you don't know how to get id, see https://github.com/w99910/laravel-notion-viewer/README.md#how-to-get-notion-page-id

document.addEventListener('DOMContentLoaded', async () => {
    await NotionViewer.render(notionPageId, document.querySelector('#index'))
});

By specifying the endPoint:

await NotionViewer.render(notionPageId, document.querySelector('#index'), 'your-end-point')
  • Renderer

You can also parse blocks on your own using Renderer class.

  • Render a notion html page with page, blocks, and parent element.

import Renderer from "notion-viewer-client/Renderer";

Renderer.renderPage(page, blocks, element)
  • Parse blocks to html

import Renderer from "notion-viewer-client/Renderer";

let output = Renderer.parseBlocks(blocks)
console.log(output);
  • Parse rich text to html

import Renderer from "notion-viewer-client/Renderer";

let output = Renderer.parseRichText(richText);
console.log(output);
  • Get a renderer of a block

import Renderer from "notion-viewer-client/Renderer";

let renderer = Renderer.getRenderer(block);
  • Callback before renderer

import Renderer from "notion-viewer-client/Renderer";

Renderer.onBeforeRender((renderer) => {
    console.log('Called before render');
})
  • Callback after renderer

import Renderer from "notion-viewer-client/Renderer";

Renderer.onAfterRender((renderer) => {
    console.log('Called after render');
})

Notion block types

The following are the block types supported by this package for now:

  • paragraph
  • heading_1
  • heading_2
  • heading_3
  • to_do
  • callout
  • code
  • image
  • has_children
  • children
  • bulleted_list_item
  • child_page
  • numbered_list_item
  • link_preview
  • toggle
  • quote
  • divider
  • table
  • table_row

Adding/Removing Renderers

  • Creating a compatible renderer
import Renderable from 'notion-viewer-client/interfaces/Renderable';

class YourCustomRenderer implements Renderable {

    render(block: Block, level?: number, containerElement?: HTMLElement): string {
        // Your code here
    }

    type() {
        return 'your_block_type';
    }

    // optional event hooks
    beforeRender(containerElement?: HTMLElement) {
    };

    afterRender(containerElement?: HTMLElement) {
    };
}
  • Adding a renderer:
import Renderer from "notion-viewer-client/Renderer";

Renderer.addRenderer(new YourCustomRenderer())
  • Removing a default renderer:
import Renderer from "notion-viewer-client/Renderer";

Renderer.removeRenderer('block_type')
  • Replacing\Removing all default renderers:
import Renderer from "notion-viewer-client/Renderer";

// Replacing renderers with your custom renders
Renderer.setRenderers([
    new YourCustomRenderer(),
    new YourAnotherCustomRenderer()
])
// Removing all renderers
Renderer.setRenderers([]);

Support Me

If you want to support me, buy me a coffee via Binance.

TODO

  • [ ] Add more renderers
  • [ ] Add tests