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

@bitsy/merge

v2.2.1

Published

merge tool for bitsy gamedata

Downloads

15

Readme

@bitsy/merge

merge tool for bitsy gamedata

notes:

  • contents which don't overlap will be added without being changed
  • contents which overlap will have their ids prefixed before being added, and references to their id will automatically be updated
  • contents which overlap but are identical will not be added (e.g. if you start from a shared file, only changes will be added on merge)
  • the contents of dialog scripts are not checked or updated; if you're referencing things from dialog (especially via hacks) you'll have to make sure that the names still line up post-merge manually
  • variables which overlap will throw an error (variable overlaps need to be resolved manually since dialog contents aren't updated)
  • title, bitsy version, and room format from game to add is ignored
  • make sure to choose a unique prefix: overlaps are not checked for prefixed conflict resolution

How To

Browser

  1. include ./dist/index.iife.js in HTML
<script src="vendor/@bitsy/merge/dist/index.iife.js"></script>
  1. reference global
const { merge } = window.bitsyMerge;

Node

  1. install
npm install @bitsy/merge --save
  1. import
const { merge } = require("@bitsy/merge");
import { merge } from '@bitsy/merge';

Use

const baseGamedata = `Write your game's title here

# BITSY VERSION 6.0...`;
const addGamedata = `Write your game's title here

# BITSY VERSION 6.0...`;
const prefix = 'added_';

const mergedGamedata = merge(baseGamedata, addGamedata, prefix).gamedata;