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

@manuscripts/assets

v0.6.4

Published

Graphical assets for the Manuscripts desktop and web applications

Downloads

124

Readme

Manuscripts graphical assets

This repository contains graphical asset originals (Symbols.sketch), as well as exports in various formats bitmap and vector formats.

Publishing

  1. npm run build to export the images from the Sketch file, generate the placeholder JS via webpack, and generate the React components via svgr (or npm run build-react if the images have already been exported).
  2. Increment the version in package.json.
  3. npm publish to publish the package to the private repository.

Resizing the React components

The width and height props are passed through to the SVG component (as are any other props), so set these to resize a component.

Styling the React components

There are no class attributes in the SVG files, but there are other CSS selectors that can be used to apply styles. For example:

const StyledIcon = styled(Icon)`
  /* SVG element selector */
  circle {
    stroke: currentColor;
  }
  
  /* id selector */
  #prefix__svg-addauthor-b {
    fill: #F00;
  }
  
  /* attribute selector */
  [fill='#FFF'] {
    fill: #FDCD47;
  }
`

Conventions

  1. Name all items you want to export meaningfully, and use for their naming a pattern like NamePatternLikeThis[@1x|2x].[pdf|svg|png], that is, all words with no separating whitespace or hyphen.
  2. Prefer symbols marked exportable over artboards marked exportable (I know this is not actually how most of the resources are exported at the time of writing, but Sketch introduced the Components Panel that makes navigating a lot easier if we use symbols).
  3. Export a 1x, 2x PNG + 1x SVG and 1x PDF from all symbols. SVG is used primarily in the web frontend, PDF in the Mac / iOS app and PNG where SVG export for some reason is not great.
  4. Do not export a JPEG unless it's for some reason needed.
  5. Export only those symbols / artboards that are actually necessary.