Listen for keyboard sequences and interpret them as a barcode.
npm install keyboard-barcode-scan-listener
Listen for barcode scan events from keyboard/HID devices in the browser.
To install via npm:
``sh`
npm install keyboard-barcode-scan-listener
To install via yarn:
`sh`
yarn add keyboard-barcode-scan-listener
To create a basic listener that uses the default input handler:
`js
import createKeyboardBarcodeScanListener from 'keyboard-barcode-scan-listener';
const removeScanListener = createKeyboardBarcodeScanListener({
onScan: (barcode) => console.log(barcode),
});
// To remove the scan listener, call the function returned by createKeyboardBarcodeScanListener:
removeScanListener();
`
By default, the scan listener will be attached to window.document and listen on keydown events.
Most of the brains in keyboard-barcode-scan-listener is in input handlers, which are initialized with the onScan handler and receive keydown events as they are received by the target; they buffer a barcode until it's fully read, at which point they call onScan.
The library ships with two handlers:
- delimited input: The default handler. Listens for a start character and buffers all input until an end character (by default, F18 and F19, respectively), when it calls onScan with the barcode. By default, it prevents barcode values from becoming input to the page.onScan` with the barcode. Does not (and cannot) prevent barcode values from becoming input to the page.
- prefixed input: Listens for a multi-character prefix (or, optionally, no prefix--not recommended!) and when the input passes a test or no input is detected for a certain amount of time, calls
Both are configurable and well-documented in the source. In general, you should prefer the delimited input handler (the default) if possible as it is more flexible and is capable of preventing scanner keyboard events from being interpreted as regular user keyboard to the page, which is generally undesirable.