Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
## Before you `start work`
Please read our contribution [guidelines](https://docs.marketprotocol.io/#contributing) and if there is a bounty involved please also see [here](https://docs.marketprotocol.io/#gitcoin-and-bounties)
If you have ongoing work from other bounties with us where funding has not been released, please do not pick up a new issue. We would like to involve as many contributors as possible and parallelize the work flow as much as possible.
Please make sure to comment in the issue here immediately after starting work so we know your plans for implementation and a timeline.
Please also note that in order for work to be accepted, all code must be accompanied by test cases as well.
### User Story
As maintainers of this package we are finding that sometime errors don't show up until we create a release and attempt to import and instantiate `Market()`.
### Why Is this Needed?
*Summary*: to ensure pre-release that everything is working.
### Current Behavior
Testing doesn't cover importing the built package and making sure all is well with MARKET.js and creating the `Market` object.
### Expected Behavior
Testing shows errors that may show up when importing MARKET.js
This may be a bit challenging, but we recently had an error that didn't show up in any of our tests like this one - https://github.com/MARKETProtocol/MARKET.js/blob/develop/test/Market.test.ts#L40 - but did fail when attempting to import into our dApp with `marketjs_1.Market is not a constructor` which had to do with wrongly importing/initialising the package ethereum-input-data-decoder
*Summary*: Create integration tests to ensure release will import and instantiate correctly.
### Definition of Done
- [ ] new tests built out for integration