pkg
Commander.js
pkg | Commander.js | |
---|---|---|
91 | 44 | |
24,099 | 26,117 | |
- | - | |
6.3 | 8.5 | |
4 months ago | 2 days ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pkg
-
We are under DDoS attack and we do nothing
I don't remember the details, and cannot find my notes on vercel/pkg. But looking at https://github.com/vercel/pkg right now I see the project has been deprecated in favour of single-executable-applications
-
Tailwind CSS v4.0.0 Alpha
> Standalone CLI β we havenβt worked on a standalone CLI for the new engine yet, but will absolutely have it before the v4.0 release.
This part is the most exciting to me. Given the rest of the release announcement, I'm assuming this means that it'll be built in Rust rather than embed Node. While I'm not a Rust zealot of anything, I'm very partial to not embedding Node. Particularly when it depends on using Vercel's now-abandoned pkg[1] tool.`
[1] https://github.com/vercel/pkg
-
Things I've learned about building CLI tools in Python
The npm package called "pkg" seems to be the standard for packaging NodeJS applications
https://www.npmjs.com/package/pkg
Unfortunately you also need to bundle all your code into a single file for it to work, but you can use any bundler (webpack, parcel, etc) you want at least
-
Deno 1.35: A fast and convenient way to build web servers
Nodejs support for "single executable applications" is getting there - this issue below is preventing wider adoption at the moment:
"The single executable application feature currently only supports running a single embedded script using the CommonJS module system."
https://nodejs.org/api/single-executable-applications.html
Should be an awesome game changer for node.js when the feature gets rounded out.
Also check out vercel's `pkg`: https://github.com/vercel/pkg/issues/1291
-
Can I include Node inside my project?
Yes, you can. Check out pkg for a fun option, which can package up your project and Node.js into a single executable.
-
[Question] How does Node-RED compile a flow?
Further, you could experiment with the pkg tool that allows you to package up Node JS, your source, and your dependencies into one single executable for easy distribution.
- Bun v0.6.0 β Bun's new JavaScript bundler and minifier
- How to restrict the access to an on premise node server?
-
Tips for reducing Docker image size
package the app using https://github.com/vercel/pkg and use a smaller base image like alpine, busybox or even scratch (if possible)
-
Making standalone exe
Check this thread: https://github.com/vercel/pkg/issues/1685
Commander.js
-
Developing a Node CLI App in an NX monorepo
Visit the Commander.js reference.
-
Next.js Codebase Analysis <> create-next-app <> index.ts explained β Part 1.3
In the previous article, I looked at a Commander to configure and accept cli options and assign it to a variable called program.
-
[AskJS] Looking for JS course for experienced developers?
You can write a command line utility using zx or commander.js. Hit a public api, spit stuff out in the console, etc.
-
[AskJS] What is your preferred solution to share and execute Node.js scripts ?
In your index.js you can do whatever you want, even create an interactive CLI (check commander).
-
Exploring video generators in FFMPEG
There is clearly a whole load of repetition, so this should be fairly easy to build and parameterise. Essentially this will all just be string building so we won't need to use any particular libraries for most of this script. We will need a way to call ffmpeg though - and ffmpeg will need to be present too, of course. To call a CLI command we can use the package commander.
-
How to Create a Testable CLI using TypeScript?
Commander.js is an NPM package that makes it easier to build CLI tools. You can find its documentation over here
-
Creating a Node.js Command-line Tool, Linux Terminal CLI and NPM Package
You can also use npm package commander to make more complex command line tool with lot of options and sub commands.
-
Create a Node.js command-line library with NRWL NX workspace
commander - npm - Required. A library that lets you define the commands and their arguments, options, help, etc.
-
Releasing package to npm
Throughout my time writing and updating my static-site generator, I've been using npm from the very foundation I use an npm package called commander. Therefore, it is obvious that for the tool that I will be using to publish my ssg, I will do so with npm.
-
Building a TypeScript CLI with Node.js and Commander
The command line has thousands of tools, such as awk, sed, grep, and find available at your disposal that cut development time and automate tedious tasks. Creating a command line tool in Node.js isn't very complicated, thanks to a powerful library like Commander.js.
What are some alternatives?
nexe - π create a single executable out of your node.js apps
oclif - CLI for generating, building, and releasing oclif CLIs. Built by Salesforce.
ncc - Compile a Node.js project into a single file. Supports TypeScript, binary addons, dynamic requires.
Ink - π React for interactive command-line apps
reverse-engineering - List of awesome reverse engineering resources
zx - A tool for writing better scripts
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
Bit - A build system for development of composable software.
bytenode - A minimalist bytecode compiler for Node.js
listr - Terminal task list
chalk - π Terminal string styling done right