FM / examples

/snap/node/11691/lib/node_modules/npm/node_modules/@pkgjs/parseargs/examples/

/snap/node/11691/lib/node_modules/npm/node_modules/@pkgjs/parseargs/examples

Name	Size	Mode	Actions
is-default-value.js	765	0644	edit dl rm
limit-long-syntax.js	1071	0644	edit dl rm
negate.js	1314	0644	edit dl rm
no-repeated-options.js	897	0644	edit dl rm
ordered-options.mjs	1396	0644	edit dl rm
simple-hard-coded.js	540	0644	edit dl rm

Edit: /snap/node/11691/lib/node_modules/npm/node_modules/@pkgjs/parseargs/examples/limit-long-syntax.js (1071B)

'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

cmd: