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

we-editool

v0.3.0

Published

light-weight, tagless and simple text edit tool!

Downloads

4

Readme

Contributors Forks Stargazers Issues MIT License

About we-editool

typing

light-weight : The package is very light, about 24KB in compression.

tagless : Users don't need to know the tags.

simple : You can use 1 component for edit text.

Getting Started

Installation

Use the package manager npm to install we-editool.

npm install we-editool
yarn add we-editool

Usage

when use WeEditor

import React from 'react';
import { WeEditor, WeEditorRef } from 'we-editor';

function ReactComponent() {
  const editorRef = useRef<WeEditorRef>(null);

  const getHTML = () => editorRef.current?.getHTML();
  const getMarkdown = () => editorRef.current?.getMarkdown();

  return <WeEditor ref={editorRef} />;
}

use your custom editor

import React from 'react';
import { WeToolbar, htmlToMarkdown, WE_EDITOR_ID } from 'we-editor';

function CustomEditor() {
  const editorRef = useRef<HTMLDivElement>(null);

  const getHTML = () => editorRef.current?.innerHTML;
  const getMarkdown = () => htmlToMarkdown(editorRef.current?.innerHTML);

  return (
    <>
      <div contentEditable ref={editorRef} id={WE_EDITOR_ID} className="editor" />
      <WeToolbar editorRef={editorRef} />
    </>
  );
}

API

WeEditor

WeEditorProps

| name | description | type | default | | --------------- | ----------------------------- | ------- | ------- | | initialHTML | initiate with html string | string? | x | | initialMarkdown | initiate with markdown string | string? | x |

WeEditorRef

| name | description | input | output | | ----------- | ------------------- | -------- | ------ | | getHTML | get html string | no input | string | | getMarkdown | get markdown string | no input | string |

WeToolbar

WeToolbarProps

| name | description | type | default | | --------- | ----------------------- | ------------------------------- | ------- | | editorRef | editor reference object | React.RefObject | x |

Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request to develop branch

License

Distributed under the MIT License. See LICENSE for more information.

Contact

JaeJun Jo - @jtree03 - [email protected]

Project Link: https://github.com/wecode-bootcamp/we-editool