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

rbxts-build

v2.2.2

Published

An opinionated build orchestrator for [roblox-ts](https://roblox-ts.com)

Downloads

127

Readme

rbxts-build

An opinionated build orchestrator for roblox-ts

Usage

Requires Node.js v14 or later.

rbxts-build works by creating several scripts inside of your package.json file's "scripts" object.

You can use rbxts-build init to automatically setup these scripts for you. It's often useful to do the following when setting up a new roblox-ts project:

  • rbxtsc init

  • npm install -D rbxts-build

  • npx rbxts-build init

  • compile

    • rbxtsc --verbose
  • build

    • rojo build --output game.rbxl
  • open

    • Launches Roblox Studio with game.rbxl
  • start

    • npm run compile
    • npm run build
    • npm run open
  • stop

    • Force kills the Roblox Studio process
  • sync

These scripts should be structured in your package.json file as:

"scripts": {
	"build": "rbxts-build build",
	"open": "rbxts-build open",
	"start": "rbxts-build start",
	"stop": "rbxts-build stop",
	"sync": "rbxts-build sync"
},

From there, you can use npm start, to launch your project.

Once you've started working, it's convenient to use npm restart (or npm res for short) to run npm stop and then npm start.

Settings

rbxts-build allows for a few settings in package.json under a "rbxts-build" key:

"rbxts-build": {
	// override arguments to rbxtsc, default provided below
	"rbxtscArgs": ["--verbose"],
	// override arguments to rojo build, default provided below
	"rojoBuildArgs": ["--output", "game.rbxl"],
	// provide a relative file location for the sync command output, default provided below
	"syncLocation": "src/services.d.ts",
	// use rbxtsc-dev instead of rbxtsc, default provided below
	"dev": false,
	// WSL-only, use .exe versions of rojo and lune, default provided below
	"wslUseExe": false,
	// run `rbxtsc -w` + `rojo serve` automatically after Studio opens, default provided below
	"watchOnOpen": true,
},

Hooks

You can run scripts before and after any rbxts-build script by adding new package.json scripts with pre- or post- suffixes.

For example:

"precompile": "echo 'pre-build command'",
"postcompile": "echo 'post-build command'",

npm will execute this as:

  1. precompile
  2. compile
  3. postcompile

Assumptions

rbxts-build assumes a few things about your project's structure:

  • Project must be a game which is fully managed by Rojo
  • Scripts are run from your project directory (where package.json lives)