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

@taller/wordpress-classic-parser

v1.0.0

Published

Parser to wordpress content originated from classic editor

Downloads

1

Readme

Wordpress Classic Parser

This lib helps to parser wordpress content generated by the Classic Editor.

For content generated using blocks we have a Wordpress package called block-serialization-default-parser to parse the content and provide structured data. However, the mentioned lib is not able to parse content generated by the Classic Editor. Then, this lib was developed to do that.

How to install

yarn add @taller/wordpress-classic-parser or

npm install @taller/wordpress-classic-parser

How to use

Using this lib is quite simple. You just need use the parse method and provide the Raw Content (that one containing shortcodes, before of being rendered).

parse(content /*: string */, options /*?: Object */);`

Parse given content, and return an object with structured content.

import { parse } from "@taller/wordpress-classic-parser";

const content = "Text\r\n[embed]https://www.twitter.com.br/some-url[/embed]";
parse(content);
/*
[
  {
    type: "paragraph",
    children: [
      {
        type: "text",
        value: "Text",
      },
      {
        type: "tag",
        tag: "br",
        attrs: {},
        children: [],
      },
      {
        type: "embed:twitter",
        value: "https://www.twitter.com.br/some-url",
        attrs: {
          named: {},
          numeric: [],
        },
      },
    ],
  },
]
*/

By default, the content provided will be preprocessed and all the breaklines (\r\n, \n, <br/>, <br /> and <br>) will be replaced for the tag <br />. Also, all the tabulation (\t) will be removed.

Options

{
    contentPreprocessor?: (content: string) => string;
    embedTypeProcessor?: (shortcode: Shortcode) => string;
}

contentPreprocessor

Allow to preprocess the content to be parsed. Receive the original content as argument. As example, if you want to replace the breaklines for <hr /> tags, you can do that:

import { parse } from "@taller/wordpress-classic-parser";

const content = "Text\r\nAnother Text";
const options = {
  contentPreprocessor: (content) => content.replace(/\r\n/, "<hr />"),
};

parse(content, options);
/*
[
  {
    type: "paragraph",
    children: [
      {
        type: "text",
        value: "Text",
      },
      {
        type: "tag",
        tag: "hr",
        attrs: {},
        children: [],
      },
      {
        type: "text",
        value: "Another Text",
      },
    ],
  },
]
*/

embedTypeProcessor

Allow to define the embed type as you need. Receive a Shortcode as argument. As example, if you want to define your custom embed type, you can do that:

import { parse } from "@taller/wordpress-classic-parser";

const content = "Text[embed]https://www.twitter.com.br/some-url[/embed]";
const options = {
  embedTypeProcessor: (shortcode) => {
    const { type } = shortcode;
    return type === "closed" ? "embed:closed" : "embed:notclosed";
  },
};

parse(content, options);
/*
[
  {
    type: "paragraph",
    children: [
      {
        type: "text",
        value: "Text",
      },
      {
        type: "embed:closed",
        value: "https://www.twitter.com.br/some-url",
        attrs: {
          named: {},
          numeric: [],
        },
      },
    ],
  },
]
*/

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -m 'feat: Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D