7 Commits (3f2a7fd6acc2a2f6698abc45aec153092a348c86)

Author	SHA1	Message	Date
Whymarrh Whitby	b6ccd22d6c	Update ESLint shared config to v3 (#9274) ... Co-authored-by: Mark Stacey <markjstacey@gmail.com>	4 years ago
Whymarrh Whitby	310b15ba4a	Fix no-plusplus issues (#9206) ... See [`no-plusplus`](https://eslint.org/docs/rules/no-plusplus) for more information. This change enables `no-plusplus` and fixes the issues raised by the rule.	4 years ago
Whymarrh Whitby	f5a125fe61	Move export defaults statements alongside their objects (#8525)	5 years ago
Whymarrh Whitby	92971d3c87	Migrate codebase to use ESM (#7730) ... * Update eslint-plugin-import version * Convert JS files to use ESM * Update ESLint rules to check imports * Fix test:unit:global command env * Cleanup mock-dev script	5 years ago
Kevin Serrano	d6286cd13a	Maintain linting.	8 years ago
kumavis	39e0a33bba	random-id - use Number.MAX_SAFE_INTEGER as max	8 years ago
Dan Finlay	8eb91e89bf	Increment tx ids to avoid collisions ... Fixes #791 It was possible for two requests to have the same ID, causing a crash and loss of StreamProvider connection. This new id generation strategy creates a random ID, and increments it for each request. In case the id generator is included from two different processes, I'm initializing the counter at a random number, and rolling it over a large number when it gets too big.	8 years ago
Dan Finlay	f229d32442	Replace old random-id code with incrementing id generator	8 years ago