bartlomieju

4 ms·

1. 1.▲
   by bartlomieju 3mo ago

   Okay I traced it, the problem is in `node_modules/vite/dist/node/cli.js`: ``` function checkNodeVersion(nodeVersion) { const major = parseInt(nodeVersion.split(".")[0], 10); const minor = parseInt(nod
2. 2.▲
   by bartlomieju 3mo ago

   Sure, we also managed to close ~30 outstanding issues with this rewrite and set us up to reach ~90% node:http compatibility, so overall I consider it a success.
3. 3.▲
   by bartlomieju 3mo ago

   We tried to build `node:http` on top of Rust libraries (like Hyper) but we failed for a couple years. So earlier this year we decided to make it compatible (by using llhttp to have very high coverage - at the moment 88% compatibility for no
4. 4.▲
   by bartlomieju 3mo ago

   > Seems like the core of these issues was a Claude-coauthored PR: https://github.com/denoland/deno/pull/33208 Disclaimer: I'm the author of the linked PR. Using AI here is not really at fault here - i
5. 5.▲
   by bartlomieju 3mo ago

   Gee, sorry to hear that. It's Bartek from the Deno team here. This is really a whack-a-mole. We currently present the latest stable Node.js version (26.3.0) so the error is not correct - I bet it's probing for something stupid lik
6. 6.▲
   by bartlomieju 3mo ago

   Bartek from Deno team hear. I'll love to hear what you feel is missing so we could improve `deno desktop` for more users.
7. 7.▲
   by bartlomieju 3mo ago

   Yes, you can do all that. You get a fully-fledged Deno program that can do all of this, _plus_ you get a frontend GUI app.
8. 8.▲
   by bartlomieju 3mo ago

   Bartek from the Deno team here. No promises yet, but we're looking into feasibility of it.
9. 9.▲
   by bartlomieju 3mo ago

   Sorry to hear that, could I ask you to file an issue in our bug tracker?
10. 10.▲
    by bartlomieju 3mo ago

    Thanks, I'll update the docs. When we wrote them a couple weeks back, Electrobun was announcing Linux only support.
11. 11.▲
    by bartlomieju 3mo ago

    Bartek from the Deno here. Nope, we do support enums OOTB.
12. 12.▲
    by bartlomieju 4mo ago

    Bartek from the Deno team here. Thanks for the feedback, I understand your frustration. > The worst of the changes is "lib.node included by default", if I'm writing Deno or web code I absolutely don't want node types
13. 13.▲
    by bartlomieju 4mo ago

    Bartek from the Deno team here. Thanks for the feedback. I assure you this is not a short-sighted change. This has been a problem since before Deno 1.0. We resorted to hacks like different set of globals for user code and different for code
14. 14.▲
    by bartlomieju 4mo ago

    Thanks for feedback, I opened a PR to implement linking functionality that seems more familiar to npm's strategy: https://github.com/denoland/deno/pull/34359
15. 15.▲
    by bartlomieju 3y ago

    Bartek from the Deno team here - we are actively working on improving experience running NextJS projects in Deno.
16. 16.▲
    by bartlomieju 3y ago

    Hi, Bartek from the Deno team here. We are actively looking into improving this situation and from initial investigations we were able to shave off roughly 40% of the baseline size, with more improvements possible in the future. Stay tuned
17. 17.▲
    by bartlomieju 3y ago

    Bartek from the Deno team here. You can also use `package.json` and bare specifiers with Deno. We also recently added `--unstable-byonm` flag (Bring Your Own Node Modules) that allows you to manage `node_modules/` be the package manage
18. 18.▲
    by bartlomieju 3y ago

    Bartek from the Deno team here. We are working on making this possible with a flag in the upcoming release.
19. 19.▲
    by bartlomieju 3y ago

    A couple months back we added an ability for Deno to run projects authored for Node.js directly. Eg. if you have a Vite app (or any other app really) with "package.json" and some "scripts" defined there, just try running
20. 20.▲
    by bartlomieju 3y ago

    Bartek from the Deno team here. Sorry to hear that - we made great progress in making Deno drop-in replacement this year, but we certainly are not yet there 100%. I'd love to hear what problems did you hit and look into solving them.
21. 21.▲
    by bartlomieju 3y ago

    Just to clarify - we do have support for node_modules/ resolution (with all of its quirks and gotchas), otherwise we wouldn't be able to load npm packages. However we made a hard stance that CommonJS is only supported in npm depen
22. 22.▲
    by bartlomieju 3y ago

    Bartek from the Deno team here, let me clarify a few things. > for one the security model is incompatible with node APIs. All Node.js APIs are polyfilled using Deno APIs and as such these Node.js API are subject to the same permission mo
23. 23.▲
    by bartlomieju 3y ago

    These modules can be included but currently there's no way to use them - that's because they need to be present on disk to load them as dynamic libraries. We're debating how to best tackle that. If you have a specific use cas
24. 24.▲
    by bartlomieju 3y ago

    It's another issue, but it's close
25. 25.▲
    by bartlomieju 3y ago

    Bartek from the Deno team here. We're currently missing polyfills for IPC module to be able to use `next dev` command.
26. 26.▲
    by bartlomieju 4y ago

    Thanks! This should be fixed now.
27. 27.▲
    by bartlomieju 4y ago

    You should be good to go after reading through the Rust book [0] and watching this video [1] [0] https://doc.rust-lang.org/book/ [1] https://www.youtube.com/watch?v=8aGhZQkoFbQ
28. 28.▲
    by bartlomieju 4y ago

    Hey, I'm the author of this blog post. Just yesterday we posted a second part of this post [0] where we add "fetch"-like API and TypeScript transpilation. Happy to answer your questions. [0] https://deno.com/b
29. 29.▲
    by bartlomieju 4y ago

    > The "npm:" import does not appear to have even started development, although it has been planned for a long time: https://github.com/denoland/deno/issues/13703 The development is well under way
30. 30.▲
    by bartlomieju 4y ago

    Yes, this effort started years ago and was ramped up significantly in recent months.