It's not like you are using any exotic js APIs but I think when publishing a package for others to use it's nice to have some sort of browser compatibility guarantee/testing. By far the simplest way to do this is to use eslint-plugin-compat and run linting with tests. This uses browserslist in package.json which is a great way to publish a contract for which browsers you want to support. Even for our own internal use it's nice to have.
I wouldn't call this high priority but it's something npm users will expect if they start using this package.
theGOTOguy
commented
3 years ago
It's not like you are using any exotic js APIs but I think when publishing a package for others to use it's nice to have some sort of browser compatibility guarantee/testing. By far the simplest way to do this is to use eslint-plugin-compat and run linting with tests. This uses
browserslistinpackage.jsonwhich is a great way to publish a contract for which browsers you want to support. Even for our own internal use it's nice to have.I wouldn't call this high priority but it's something npm users will expect if they start using this package.