pyr0ball
7a704441a6
- web/: Vue 3 + Vite + UnoCSS + Pinia, dark tactical theme (amber/#0d1117) - AppNav, ListingCard, SearchView with filters/sort, composables (useSnipeMode, useKonamiCode, useMotion), Pinia search store - Steal shimmer, auction countdown, Snipe Mode easter egg all native in Vue - docker/web/: nginx + multi-stage Dockerfile (node build → nginx serve) - compose.yml: api (8510) + web (8509) services - Dockerfile CMD updated to uvicorn for upcoming FastAPI layer - Clean build: 0 TS errors, 380 modules
35 lines
1 KiB
JavaScript
35 lines
1 KiB
JavaScript
'use strict';
|
|
|
|
// This is an example of using tokens to add a custom behaviour.
|
|
//
|
|
// Require the use of `=` for long options and values by blocking
|
|
// the use of space separated values.
|
|
// So allow `--foo=bar`, and not allow `--foo bar`.
|
|
//
|
|
// Note: this is not a common behaviour, most CLIs allow both forms.
|
|
|
|
// 1. const { parseArgs } = require('node:util'); // from node
|
|
// 2. const { parseArgs } = require('@pkgjs/parseargs'); // from package
|
|
const { parseArgs } = require('..'); // in repo
|
|
|
|
const options = {
|
|
file: { short: 'f', type: 'string' },
|
|
log: { type: 'string' },
|
|
};
|
|
|
|
const { values, tokens } = parseArgs({ options, tokens: true });
|
|
|
|
const badToken = tokens.find((token) => token.kind === 'option' &&
|
|
token.value != null &&
|
|
token.rawName.startsWith('--') &&
|
|
!token.inlineValue
|
|
);
|
|
if (badToken) {
|
|
throw new Error(`Option value for '${badToken.rawName}' must be inline, like '${badToken.rawName}=VALUE'`);
|
|
}
|
|
|
|
console.log(values);
|
|
|
|
// Try the following:
|
|
// node limit-long-syntax.js -f FILE --log=LOG
|
|
// node limit-long-syntax.js --file FILE
|