-
Notifications
You must be signed in to change notification settings - Fork 24
Update typescript and devDependencies #32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This creates a bit more concise js output from TypeScript. My main intention was to remove rollup from this project as tsc supports umd output too. But for some reason the umd output doesnt seem to work with the tests as the import seems to be different with rollup. Dropping support for old JS and using ES modules rather than umd would simplify the toolchain here. ES modules are supported from Node.js 12 which is also many years out of support already. All browsers support ES modules for years now so requiring ES modules shouldnt be a big problem. But for this PR I stayed with bumping the dependencies.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@EdJoPaTo Thanks!
"KaitaiStream.js", | ||
"KaitaiStream.d.ts", | ||
"index.d.ts" | ||
"*.js", | ||
"*.d.ts" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, I don't think this the best idea - it makes it possible (and easy) to accidentally publish some other .js
file. Let's keep it explicit.
This creates a bit more concise JS output from TypeScript.
My main intention was to remove rollup from this project as tsc supports UMD output too. But for some reason the UMD output doesn't seem to work with the tests as the import seems to be different with rollup. Dropping support for old JS and using ES modules rather than UMD would simplify the toolchain here.
ES modules are supported from Node.js 12 which is also many years out of support already. All browsers support ES modules for years now so requiring ES modules shouldn't be a big problem. But for this PR I stayed with bumping the dependencies.
As the initial TypeScript implementation came from @Tschrock in #25 I'll tag you here too as you might be interested.