What I don't like is that I have to use the ! non-null assertion operator, even if it is clear that the bignumber property should be non-null (as per the bignumberDependencies object passed to create).
Thanks for reporting Paul. It would be nice if it's possible to improve the type definitions. Anyone able to look into this? Help would be very welcome.
I followed the custom bundling docs and created my own instance of math.js, like this:
What I don't like is that I have to use the
!
non-null assertion operator, even if it is clear that thebignumber
property should be non-null (as per thebignumberDependencies
object passed tocreate
).I further had to disable the @typescript-eslint/no-non-null-assertion ESLint rule, because the lint task was failing.
My feature request: let the compiler know that the objects returned by
create
are non-null, based on the inputs provided.