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

@shelf/trim-around-tag

v3.0.0

Published

Trims text to max length around custom HTML tag

Downloads

5,195

Readme

trim-around-tag CircleCI npm (scoped)

Trims text to max length around custom HTML tag

Install

$ yarn add @shelf/trim-around-tag

Usage

const {trimTextAroundTag} = require('@shelf/trim-around-tag');

trimTextAroundTag({
  // Long text to trim around HTML tag
  // There is <em> text somewhere inside
  text: 'The storm was rapidly intensifying at the time, after the wind shear had decreased,[2] and the eye contracted to a diameter of 19 km (12 mi).[10] At 09:00 UTC on October 28, the IMD upgraded Nilofar further to an extremely severe cyclonic storm.[2][nb 1] Six hours later, the JTWC estimated peak 1-minute winds of 215 km/h (130 mph);[5] at the time, the agency anticipated further strengthening due to the favorable conditions and good organization.[12] At 18:00 UTC on October 28, the IMD estimated peak 3-minute winds of 205 km/h (125 mph).[2] At the time, it was the <em>third</em>-<em>strongest</em> storm on record in the Arabian Sea.[13] On October 29, Nilofar started weakening due to increased wind shear, and the convection diminished in intensity.[14] At the same time, the storm turned northeastward while rounding the ridge to the east.[15] Increasingly cooler and drier air, as well as cooler waters, caused the storm to degrade rapidly.[2] The eye, previously small and well defined, dissipated by 06:00 UTC on October 29.[16] Lateras well as cooler waters, caused the storm to degrade rapidly.[2] The eye, previously small and well defined, dissipated by 06:00 UTC on October 29.[16] Later',
  // Max length of chars to leave around HTML tag
  maxLengthAround: 200,
  // Max total length of resulting string
  maxTotalLength: 500,
  // HTML tag to trim text around
  tag: 'em',
  //(Optional) add '...' from cut side
  omission: '...',
});
//=> anticipated further strengthening due to the favorable conditions and good organization.[12] At 18:00 UTC on October 28, the IMD estimated peak 3-minute winds of 205 km/h (125 mph).[2] At the time, it was the <em>third</em>-<em>strongest</em> storm on record in the Arabian Sea.[13] On October 29, Nilofar started weakening due to increased wind shear, and the convection diminished in intensity.[14] At the same time, the storm turned northeastward

The storm was rapidly intensifying at the time, after the wind shear had decreased,[2] and the eye contracted to a diameter of 19 km (12 mi).[10] At 09:00 UTC on October 28, the IMD upgraded Nilofar further to an extremely severe cyclonic storm.[2][nb 1] Six hours later, the JTWC estimated peak 1-minute winds of 215 km/h (130 mph);[5] at the time, the agency anticipated further strengthening due to the favorable conditions and good organization.[12] At 18:00 UTC on October 28, the IMD estimated peak 3-minute winds of 205 km/h (125 mph).[2] At the time, it was the <em>third</em>-<em>strongest</em> storm on record in the Arabian Sea.[13] On October 29, Nilofar started weakening due to increased wind shear, and the convection diminished in intensity.[14] At the same time, the storm turned northeastward while rounding the ridge to the east.[15] Increasingly cooler and drier air, as well as cooler waters, caused the storm to degrade rapidly.[2] The eye, previously small and well defined, dissipated by 06:00 UTC on October 29.[16] Lateras well as cooler waters, caused the storm to degrade rapidly.[2] The eye, previously small and well defined, dissipated by 06:00 UTC on October 29.[16] Later

...further strengthening due to the favorable conditions and good organization.[12] At 18:00 UTC on October 28, the IMD estimated peak 3-minute winds of 205 km/h (125 mph).[2] At the time, it was the <em>third</em>-<em>strongest</em> storm on record in the Arabian Sea.[13] On October 29, Nilofar started weakening due to increased wind shear, and the convection diminished in intensity.[14] At the same time, the storm turned...

Publish

$ git checkout master
$ yarn version
$ yarn publish
$ git push origin master --tags

License

MIT © Shelf