Dilīp Shukla (दिलीप शुक्ल)@fusionstringsDec 4, 2025Absolutely but somehow developers don't like standards until backed up by popular frameworks.Haz@diegohazDec 4, 2025Use the standard Node.js "imports" field instead of TypeScript aliases:40
Dilīp Shukla (दिलीप शुक्ल)@fusionstringsNov 8, 2024HTML ☀️ Paper page - HtmlRAG: HTML is Better Than Plain Text for Modeling Retrieved Knowledge in RAG SystemsFrom huggingface.co14
Dilīp Shukla (दिलीप शुक्ल)@fusionstringsMay 2, 2024any server-side code must narrow the gap to browser JavaScript Ryan Dahl: From Node.js and Deno to the ‘Modern’ JSR RegistryFrom thenewstack.io20
![A side‑by‑side code comparison showing migration from TypeScript path aliases to Node.js imports. On the left, tsconfig.json defines `"paths": { "@/ *": ["./ *"] }`, used as `import "@/foo"`. On the right, package.json defines `"imports": { "#app/ *": "./ *" }`, used as `import "#app/foo"`. Red arrows point from the TS config to the package.json config and from the old import style to the new one.](https://pbs.twimg.com/media/G7VyfHfbsAEUHEr?format=webp&name=large)
