react-notion-x VS prettier

Formatting the API response (eg. from https://developers.notion.com/reference/retrieve-a-block) is tough, so I want to use a community-maintained package like https://github.com/NotionX/react-notion-x. Most Notion API users use Notion as a website builder so almost all the packages are in React.js or Next.js

I love coming across a great blog like this an realizing it was built using two of my open source repos:

- https://github.com/transitive-bullshit/nextjs-notion-starter...

- https://github.com/NotionX/react-notion-x

Using this library, you can easily get data from Notion Pages.

I used an open source Notion library that I'm a main maintainer of called React-Notion-x. It takes Notion data and turns it into html blocks that you can add to your website.

Long: Looks like he is using Notion as a CMS (using something like https://github.com/NotionX/react-notion-x) for his site and not the actual Notion share feature, seen by that the page names are not included in the urls (and that he is using NextJS for his site).

For reference, we're using the notion-compat tool from the react-notion-x package.

There are already existing libraries that wrap it, you can search them on Github, for example this one https://github.com/NotionX/react-notion-x

In my previous article in this series, I had created my own react components to work with the Notion API due to the lack of a recognized renderer that works with Official Notion API. I came across the react-notion-X library but that did not use the Official Notion API then so I chose to create my own renderer. But soon after I published that article, Travis Fischer (creator of react-notion-x and a couple of really handy tools) added support for the official Notion API with notion-compat (still a WIP) which allows you to use react-notion-x’s powerful react renderer with the official API. So I replaced my renderer components with the react-notion-x renderer which gave me a huge performance boost.

Yes, it's using Notion as a CMS + react-notion-x (1) + some custom styling.

(1) https://github.com/NotionX/react-notion-x

From my point of view, Prettier doesn't work well for styling with utility classes. For a discussion see Prettier#7863 or Prettier#5948.

Prettier: An opinionated code formatter that enforces a consistent code style.

Automating code checks with static code analysis allows us to enforce code styling effectively. By integrating tools into our workflow, we can identify errors at an early stage, while coding instead of blocking us at the end. For instance, flake8 checks Python code for style and errors, eslint performs similar checks for JavaScript, and prettier automatically formats code to maintain consistency.

So anyways, I wanted to hook up Emacs with Astro support. For now, I've just been roughing it out there and running Prettier by itself and turning off save on format and auto-complete. It's been scary.

If you're a developer, you're surely familiar with Prettier and ESLint. With over 8 years of existence, they have established themselves as references in the JavaScript ecosystem.

prettier is used to format you text

No formatting inconsistencies: The committed code should follow the organization's code formatting standards(prettier or pretty-quick).

Let’s walk through the steps for a one-time setup to configure husky pre-commit and pre-push hooks, ESLint with code styles conventions, prettier code formatter, and lint-staged. Husky automatically runs a script on each commit or push. This is useful for linting files to enforce code styles that keeps the entire code base following conventions.

GitHub | Website

Prettier: An opinionated code formatter that enforces a consistent code style.