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

react-native-tc-conversations-test-2

v0.6.8

Published

## Getting started

Downloads

94

Readme

react-native-tc-conversations

Getting started

When developing/testing this module locally you will need to use the comms app.

Building

There is a script under /build/buildAndPublish.sh that will copy files accordingly into /staging folder and even auto increment and publish to npm.

Depending if the first parameter web was passed to the script, it will either remove the .web.tsx extentions of certain files or rename them to drop the .web, thus replacing the original file.

If a second parameter major | minor | patch is patched, it will also call npm version {parameter} and npm publish afterwards to automatically publish a release. Remember to also update /build/package.native.json and build/package.web.json to reflect this latester version number.

To build:

  1. Run npm run prep for native, npm run prep web for web bundling
  2. This will copy files into the staging folder and run npm run build against it

To publish/release:

  1. Ensure you are logged into npm via npm login - ask the team for the credentials.
  2. Ensure the npm versions in package.native.json and package.web.json is set to the current released version.
  3. Run npm run publishWeb {parameter} or npm run publishNative {parameter} where parameter is as described above to increment the version number and publish to npm, ie. npm run publishWeb patch