Replies: 2 comments 2 replies
-
|
This looks like a resolution bug. Deno supports built-in Node, I need to debug more, but the way it's "require"d is a bit funky: ...
Object.defineProperty(exports, "__esModule", ({ value: true }));
exports.deflateDatasetFlow = exports.toUtf8Flow = exports.toIndeterminateLengthSequences = exports.fmiGroupLengthFlow = exports.validateContextFlow = exports.ValidationContext = exports.headerFilter = exports.fmiDiscardFilter = exports.groupLengthDiscardFilter = exports.denyFilter = exports.allowFilter = exports.tagFilter = exports.stopTagFlow = exports.toBytesFlow = void 0;
const stream_1 = __webpack_require__(/*! stream */ "stream");
const zlib_1 = __importDefault(__webpack_require__(/*! zlib */ "zlib"));
const base_1 = __webpack_require__(/*! ./base */ "./src/base.ts");
const character_sets_1 = __webpack_require__(/*! ./character-sets */ "./src/character-sets.ts");
...It might have to do with |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
I made this site to track Deno compatibility every day: https://github.com/ffMathy/is-deno-compatible-yet |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am curious about deno and I am trying to convert a simple script, but I am hitting a snag at the very first line.
Which gives:
on
Perousing the code I had the feeling deno should provide the necessary polyfill for zlib? Am I missing something? Aren't node modules loaded with
npm:supposed to have these shims enabled?Beta Was this translation helpful? Give feedback.
All reactions