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

@mediafly/js-ui

v51.1.2

Published

UI components for Mediafly Angular applications

Downloads

1,002

Readme

mediafly-js-ui

UI components for Mediafly apps.

View changelog

Build Status

Getting started

Match your Node version to the contents of .node-version in the project root and run npm ci to install dependencies.

You'll also need to be authenticated to the Mediafly NPM org.

Working locally

Add 127.0.0.1 local.imediafly.com to your hosts file.

Run the site locally: npm start

Run unit tests once: npm test

Run Karma server to develop unit tests with hot reload: npm run karma

Run e2e tests with Cypress: npm start then npm run cypress in a 2nd terminal

Landing & releasing a new version

  1. Merge your feature branch. Ideally, squash the branch and put a useful summary in the commit message.
  2. Switch to main and add an entry in CHANGELOG.md, under the version that will be released.
  3. Stage the changelog modification, but don't commit.
  4. Run npm run release and follow the prompts. By default this will be a patch release. To do a major/minor release, pass the flag like this: npm run release -- major.

Updating the mfly webfont

  1. Go to the IcoMoon App: https://icomoon.io/app/#/select
  2. Click "import icons" and select src/fonts/mfly-webfont-v1.x.json. This will load the font project.
  3. Drag the new SVG into the project and click it to add it to the font (it will turn white with an orange border).
  4. Click the hamburger icon on the top right of the mfly-webfont section. Select "Download JSON".
  5. Increment the version number and add this to the file name (if the old json was named v1.5, you would add -v1.6 to the new json).
  6. Add this file to the project in src/fonts and delete the previous json file.
  7. Back in IcoMoon, at the bottom of the window, click "Generate Font".
  8. Hit the settings gear next to the Download button. Update the version in this window. Set the prefix to mfly-font and the name to mfly-webfont.
  9. Hit download. Unzip this archive. Copy the .woff file into src/fonts, overwriting the old font file.
  10. Next, update src/components/less/fonts/mfly-webfont.less by adding the new glyph name and its codepoint (ex: e907). You can find these on the "Generate Font" page in IcoMoon.
  11. Add an example of the new glyph in app/basics/webfont/webfont.page.html to make sure the font works end-to-end.

Now you should be good to go! Check this all in and do a release.