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

expo-updater

v2.0.3

Published

Update package.json to use latest Expo SDK

Downloads

30

Readme

expo-updater

Update package.json to use new Expo SDK

Install

$ npm install --global expo-updater

Usage

Goto the project root & run

$ expo-updater

:warning: Warning ️

Original Implementation was made to be automated, but the Expo team changes versions continuously so the original implementation didn't work when version 24.0.1 was published so I've changed the implementation to use a expo.json file which will be using a JSON file maintained by me until I am using Expo. You can fork this repo to use your own if I stop maintaining. Follow the below steps to use your own local version.

Symlink

  1. If you want to use your own version, just clone it or download it.
  2. cd expo-updater
  3. npm install
  4. npm link to create a symlink to expo-updater
  5. Now change the index.js file or expo.json file & then repeat Step 4 again & it will use your own version.

Related

Surrender - CLI script that clears Watchman, removes node_modules and cleans cache using npm or yarn

Contributing

Contributions are welcome!

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

Or open up a issue.

License

MIT © Akshay Kadam