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

@hhhallan/notion-parse-mdx

v0.0.14

Published

Convert Notion pages to Markdown with frontmatter - (Kodaps) / Convert to MDX pages - (hhhallan)

Downloads

5

Readme

notion-parse

An NPM module for downloading and Notion content and saving it as Markdown for NextJS. In short this takes the data from a page in a database and saves the data as FrontMatter and the content as Markdown. The second part is done by the excellent notion-to-md module.

I use this to download my Notion content and save it as Markdown for my NextJS blog. It's a work in progress, but it's working for me so far.

I also use ContentLayer to make sure my fontmatter has the right fields.

Usage

Here is how I use the module in my NextJS project.

I have a .env file with the following variables :

NOTION_SECRET=secret_blablablablabla

NOTION_PORTFOLIO_DATABASE_ID=18abababababababababba
NOTION_NEWSLETTER_DATABASE_ID=19abababababababababba
NOTION_POST_DATABASE_ID=20abababababababababba

I then have this script that I run to download the content from Notion and save it as Markdown :


// @ts-check

const NotionParse = require('@kodaps/notion-parse');
const dotenv = require('dotenv');

dotenv.config();

const go = async () => {

  if (process.env.NOTION_SECRET) {
    await NotionParse.parseNotion(process.env.NOTION_SECRET, './src/content', [
      {
        databaseId: process.env.NOTION_PORTFOLIO_DATABASE_ID || '',
        contentType: 'Portfolio'
      },
      {
        databaseId: process.env.NOTION_POST_DATABASE_ID || '',
        contentType: 'Post',
        languageField: 'lang',
        filterFields: [ 'translation', 'createdAt', 'status', 'Type']
      },
    ])
  }

};

go().then(() => {
  console.log('Done');
});

This supposed several things :

  1. that the files are stored in a subfolder of the folder passed in as parameter (here ./src/content) based on the content type
  2. that the ContentLayer type names map to the subfolders. So for instance for the Post content type, the files will be stored in ./src/content/post
  3. that the Notion token and database IDs are stored in environment variables, and that there is one database per content type
  4. That the title of the content is stored in a 'title' field in Notion