Traveler isn't available on npm and doesn't look like it ever has been so I'm a bit confused why it's listed here as an example. If there are other screepers-maintained npm packages we could list them here as an example, but a cursory glance didn't turn any up.
Running `npm run push-main` gives this with nodejs 17:
> Package subpath './package.json' is not defined by "exports" in /home/wouldntyouliketoknow/node_modules/tslib/package.json
This change incorporates [the fix](https://github.com/ezolenko/rollup-plugin-typescript2/issues/286) from rollup-plugin-typescript2 v0.31.0.
* Update .eslintrc.js to prevent false positives
Utilizing eslint "no-shadow" rule yields false positives for enums (claims that they were declared in an upper scope, error "no-shadow"
Utilize @typescript-eslint/no-shadow corrects this issue.
https://github.com/typescript-eslint/typescript-eslint/issues/2483
As prompted by eduter on Discord, Node 10 (current game runtime)
supports es2018. This is also confirmed by this stackoverflow post[1]
and node.green [2].
This also sets the lib to "es2018" vs "esnext". With esnext it's
possible to reference standard library functions that don't exist in
es2018 and are not polyfilled by tsc. Ex. String.prototype.matchAll from
es2020. This would cause a runtime error.
If users of this library want to provide their own polyfills, they can
change the lib back to "esnext" or some other future version.
[1] https://stackoverflow.com/questions/51716406/typescript-tsconfig-settings-for-node-js-10
[2] https://node.green/#ES2018
Updates Typescript to ^4.3.5, previously would not pull version 4
Updates eslint related packages and prettier
Updates rollup related packages
Thanks #192
Updates the linting docs for the change to ESLint. Replaces the package
name, renames relevant rules and updates all external URLS to reference
eslint.org
Fixes#149
This attempts to reduce the amount of redundant ESLint rules we
currently have. It also upgrades the ESLint TypeScript parser to a newer
version (3.7.0).
