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

@wmdmark/syncmycode

v0.6.5

Published

A simple way to sync local javascript projects

Downloads

13

Readme

NPM Version

What

Sync My Code is an unorthodox but pragmatic way of sharing code between different projects and keeping them in sync. Think of it as a poor man's Bit.dev.

Here's what it does:

  1. Watches and copies external project source code to your local project.
  2. Checks your local package.json for mismatches and optionally updates it for you.
  3. Allows syncing changes from your local copy back to the external projects or reverting them back to the external source.

Why?

  • We needed a simple way to share our code libraries across multiple projects (and not just in a mono repo).
  • We wanted a "native" developer experience where the library code changes are immediately built/hot reloaded just like local code.
  • We needed a way to push changes from a local copy back to the source.

There may be a better way to do what we're doing here, but I haven't found any with a good DX for our small team of devs. That said, this very well may not scale to larger teams.

How

1) Install

npm install -g @wmdmark/syncmycode

2) Setup a config file

Create a sync.json file in the root of the project you want to sync code to. For each external project, add an entry to syncers section.

Each syncer should have the following fields:

  • root: Relative path to the root of the project (where the folder that holds it's package.json)
  • source: The relative path (from root) that you want to sync source code from
  • destination: The folder want to sync the source code to.
  • name (optional): A name for the package in your local project. Defaults to the name in package.json.

Example:

{
  "syncers": [
    {
      "root": "../fire-ui",
      "source": "src",
      "destination": "./lib"
    },
    {
      "root": "../fire-utils",
      "source": "src",
      "destination": "./lib"
    }
  ]
}

3) Sync!

Simply run

syncmycode

This will check your source paths as well as recommend any changes that need to be made to your local package.json projects to support the synced libraries.

You can also specify a different location for the sync config file by adding a --config my-sync-config.json.

If you want to disable initial setup prompts (for updates to package.json and creating a VSCode workspace), pass --skip as an option.

Additonal Tips

  • If you happen to edit the local copy of the external code. Simply run syncmycode again and it will detect any newer local changes and ask how you want to resolve them.