build for non-node targets (standard levels and browsers using caniuse info)

my idea would be that you define a “modernness” level that you want to require and then compile to be understood by engines which are at least that modern.

e.g. moving targets like “newest release of up-to-date browsers” or static targets like “ES5-compatible JS engines”

No files, tests, or entry points are named. Start by examining how the project currently compiles its ES* bundle for the NodeJS version during installation, then determine how browser targets, standard levels, and caniuse data would fit; done would require a defined target-selection mechanism and compilation behavior for the requested targets.

Written by the indexing model from the issue text.