Issue since change on deno polyfill

[RoXuS]

Hey team,

Since change on deno polyfill (last commits) we have an issue when we use our package from esm:

Example of usages:
export { parseStringPromise } from "https://esm.sh/xml2js@0.4.23";

[RoXuS]

any way to stay on v15?

Something like this
export { parseStringPromise } from "https://esm.sh/v15/xml2js@0.4.23";

[shadowtime2000]

@RoXuS Try importing from like https://cdn.esm.sh/v15/xml2js@0.4.23 or something like that

[RoXuS]

yeah it is ok with v15!

[RoXuS]

But we have to focus the file directly

https://cdn.esm.sh/v15/xml2js@0.4.23 -> redirect to v16
https://cdn.esm.sh/v15/xml2js@0.4.23/esnext/xml2js.js -> ok on v15 (but types are KO)

[ije]

i will revert the v15's polyfills since the deno/std/node is not stable.

[RoXuS]

i will revert the v15's polyfills since the deno/std/node is not stable.

you can't enable v15 and v16 at same time?

[ije]

i just disabled the events polyfill of std/node, please try again deno --reload

[RoXuS]

I get

During aleph build...

[ije]

fixed