Pull requests are welcome, but please keep the following in mind:

• Backwards-compatibility-breaking changes will not be accepted; they may be considered for the next major version
• Security is important; adding dependencies require fairly convincing arguments as to why
• The library aims to be lean, so keep an eye on the dist/ethers.min.js file size before and after your changes (the build-clean target includes these stats)
• Keep the PR simple, readable and confined to the relevant files; see below for which files to change
• Add test cases for both expected and unexpected input
• Any new features need to be supported by me (future issues, documentation, testing, migration), so anything that is overly complicated or specific may not be accepted
• Everyone is working hard; be kind and respectful

It is always highly recommended that you open a Ethers Discussion before beginning a PR.

The documentation is an area which can always benefit from extra eyes, extra knowledge and extra examples.

Contributing to the documentation is welcome, but when making changes to documentation, please ensure that all changes are made only to:

• Updating /docs.wrm/**.wrm
• Adding links: /docs.wrm/links/*.txt
• Updating API jsdocs: /** ... */ comment blocks within /src.ts/

Generally changes to /docs.wrm/config.wrm should not be made, and if you feel it is necessary, please consider opening a Ethers Discussion first.

Similarly, when adding a new sections, a Ethers Discussion is preferred.

All changes should be in the Flatworm Markdown Dialect.

Currently, the documentation is built using an experimental v2 of the Flatworm documentation system, a system originally specifically made to maintain the Ethers documentation.

The new tsdocs branch has the ability to parse jsdocs from from TypeScript source files to create an API reference.

In general the only files you should ever include in a PR are:

• TypeScript source: /src.ts/**.ts

Do not include a package.json with the updated tarballHash or version, and do not include any generated files in your PR.

A bug fix must not modify anything requiring a minor version bump (see Contributings and Hacking), such as changing a method signature or altering the exports.

Contributing new features usually require a deeper understanding of the internal interactions with Ethers and its components, and generally requires a minor version bumpincludes anything w

When making any of the following changes, you must first open a Ethers Discussion as the minor version will need to be bumped.

• any signature change (such as adding a parameter, changing a parameter type, changing the return type)
• adding any new export; such as a class, function or constants
• adding any method to any class
• changing any exports property within the package.json

Changes of this sort should not be made without serious consideration and discussion.