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

x4build

v1.5.26

Published

x4js solution builder, server and hmr, cli command line

Downloads

69

Readme

x4build

x4 solution builder

installation:

npm install -g x4build@latest

as an alternative, you can use npx ; use npx x4build instead of x4build.

CREATE a new project

	# create an empty electron project
	# this will create a new folder named test with all files to start a new electron project
	x4build create test --type=html
  • --type=<type> where <type> is one of

    • node: node project (client and server)
    • electron: electron project (desktop application)
    • html: html project (standard html project)
    • server: simple server (work in progress)
  • --overwrite: to overwrite existing project

BUILD an existing project

	# build an electron project and monitor the main.js file
	# kill & reload main.js when changing
	x4build build --serve --watch --hmr
  • --release: build the release

  • --debug: build in debug mode (default)

  • --serve: (html) serve files

  • --watch: watch for source modifications (automatic rebuild)

  • --hmr: (electron/html) Hot Module Reloading: reload the browser when build is done

  • --monitor=: (node) monitor for file modification kill and reload the node application

package.json

a new entry is recognized: x4build

  • postBuild: commands to start after compilation; some string parts are replaced:

    • ${srcdir}: source dir
    • ${outdir}: destination dir
    • @copy: simple copy command line(windows/linux compat)
  • external: don't bundle these elements (you must use npm install for them in the dist folder)

  • override: all options that will be sent to esbuild

example:

"x4build": {
	"postBuild": [ "@copy ${srcdir}/src/assets ${outdir}/assets" ],
	"external": [ "better-sqlite3" ],					
	"override": {
		"legalComments": true
	}
}