Skip to content

Conversation

@vbudovski
Copy link
Contributor

@vbudovski vbudovski commented Jan 11, 2025

This adds the Paseri parsing library to the benchmark.

@vbudovski vbudovski force-pushed the feature/paseri2 branch 4 times, most recently from 4145154 to dd39245 Compare January 11, 2025 23:40
@vbudovski
Copy link
Contributor Author

@moltar I’ll sort out the merge conflicts in a bit, but are there any issues with this new approach?

@vbudovski vbudovski force-pushed the feature/paseri2 branch 2 times, most recently from 31c01df to 5fe1c38 Compare January 13, 2025 06:04
@moltar moltar requested review from DarkGL and hoeck January 13, 2025 20:10
"docs:watch": "tsc --project tsconfig.docs.json --watch --preserveWatchOutput & serve docs",
"docs:build": "tsc --project tsconfig.docs.json",
"compile:deepkit": "deepkit-type-install && rimraf cases/deepkit/build && tsc -p cases/deepkit/tsconfig.json",
"compile:paseri": "rimraf cases/paseri/build && esbuild cases/paseri/src/index.ts --bundle --minify --platform=node --outdir=cases/paseri/build && tsc --emitDeclarationOnly cases/paseri/src/index.ts --outDir cases/paseri/build",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is the esbuild buildstep necessary? is it because paseri targets deno and won't run on node without compiling?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nothing to do with Deno. Paseri is ESM-only, while this library is CJS. You can’t mix import types, so we need to recompile it to CJS to match.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yeah of course. Another maintenance task incoming: switch to ESM 😁

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See my previous PR where I did just that 😂

},
"include": ["**/*.ts"]
"include": ["**/*.ts"],
"exclude": ["cases/paseri/src/*.ts"]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Things getting complicated here @moltar.

Would be nice to have some kind of isolation for all the libraries 😁. I have the feeling that sooner or later we'll have some problems due to having all those libraries in a single npm project.

@hoeck
Copy link
Collaborator

hoeck commented Jan 15, 2025

@moltar I’ll sort out the merge conflicts in a bit, but are there any issues with this new approach?

Never heard of jsr.io before but it looks good to me 👍.

Let me know if you need help with resolving the conflict 😄.

@vbudovski
Copy link
Contributor Author

@DarkGL Could I get your review also please?

@DarkGL
Copy link
Collaborator

DarkGL commented Jan 16, 2025

@vbudovski will do it tomorrow

@hoeck hoeck merged commit 16203f7 into moltar:master Jan 17, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants