`opCodes/configError"' has no exported member 'OP_SOURCE_UNAVAILABLE'.` etc about io HOT 4 CLOSED

Thanks @stazz! Personally I don't think it's 100% necessary and would probably end up complicating our CI pipeline. We're pretty careful about only exposing things from the library that are going to end up in the declaration files.

That being said - I'll leave it up to @mikearnaldi for the final word.

from io.

@mikearnaldi - given that our build process in-lines the op codes anyways, we should probably just consider removing op codes entirely.

from io.

@leighman - I believe this should be closed by 985dca4 once released. Going to close this issue. Thanks for the report!

from io.

@IMax153 Would it make sense to add a step into CI/CD pipeline, which would try to compile a simple TypeScript file, which would just import the .d.ts code produced by compilation of the source code in this repo? That would help to avoid similar errors in the future. At least I use similar approach in my own libraries, and it has helped me catching few similar errors to this one.

I can open separate ticket for that if you think that's good idea. Maybe even make a PR :)

from io.