Ambiguity around intended runtime environment of these packages about asn1-schema

[MasterKale]

BTW here are some package versions I'm seeing in node_modules/ tonight on a fresh npm install based on those three "asn-" packages defined above:

• @peculiar/[email protected]
• @peculiar/[email protected]
• @peculiar/[email protected]
• [email protected]

One nuance to all of this is that I don't ship package-lock.json's with my libraries, so consumers (and CI) can pick up the latest versions of my library's dependencies on every install. In this case it's causing unexpected CI failures despite no code changes after a previous successful CI run, because I waited three weeks between CI runs and these packages happened to get updated in that time. I think that means it's something that changed in asn1js between now and April 27?

[microshine]

I've updated and published all @peculiar/asn1 packages. Now it uses ES2019 lib and BufferSource from pvtsutils module.

Please try the new version.

Successfully published:
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]
 - @peculiar/[email protected]

[MasterKale]

I forgot to follow up, thank you very much @microshine for such a speedy response and resolution. I'm happy to report that 2.1.7 fixed the problem 😌