tsconfig-paths
tsx
tsconfig-paths | tsx | |
---|---|---|
5 | 24 | |
1,768 | 7,841 | |
0.8% | 5.2% | |
1.0 | 9.2 | |
21 days ago | 4 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tsconfig-paths
-
ERDIA: TypeORM entity specification documentation tool
If you've use a re-map path in your project, you have to pass it up to tsconfig-paths like this,
-
The Native Way To Configure Path Aliases in Frontend Projects
There are multiple libraries available for configuring path aliases in Node.js, such as alias-hq and tsconfig-paths. However, while looking through the Node.js documentation, I discovered a way to configure path aliases without having to rely on third-party libraries. Moreover, this approach enables the use of aliases without requiring the build step.
-
How to write path.resolve cleaner?
If you're not using webpack, you can give tsconfig-paths a try.
-
Ultimate Node.js starter that scales with DI, native TypeScript, super fast unit tests and all batteries included
Path mapping Very handy tsconfig-paths library allows to import modules from the filesystem without prefixing them with "./".
-
Use ts-node to run code across multiple monorepo packages
was just dealing with this yesterday. You need to use this package: https://github.com/dividab/tsconfig-paths
tsx
-
Finally, a guide for Node.js and TypeScript and ESM that works
I really enjoy frontend/node/typescript development. I roll my eyes whenever the HN-types complain about CSS or frontend development being a hellhole. Mostly the comments I see seem ignorant or impatient ("Why doesn't this thing work without be bothering to learn it?")
However, the intersection of typescript, nodejs, and ES modules is consistently the most frustrating experience I ever have. Trying to figure out which magic incantation of tsconfig/esbuild/tsc/node options will let me just write code and run it is a fools errand. You might figure something out, and then you try to use Jest and then you descend into madness again.
The biggest tip I can give people is to ditch ts-node and just use (the awkwardly named) tsx https://github.com/privatenumber/tsx, which pretty much just "mostly works" for running Typescript during dev for node.
The problem mostly seems to stem for all the stakeholders being pretty dogmatic to whatever their goals are, rather than the pragmatic option of just meeting people where they are. I really wish the Node, Typescript, Deno/Bun, and maybe some bundler people would come together and figure out how to make this easier for people.
-
ERDIA: TypeORM entity specification documentation tool
If your TypeORM entity is written in TypeScript, you have to run ERDIA using ts-node or tsx as follows.
-
xtsz - a TS / JS file runner with support for HTTP/S imports
Want to import a package / file conveniently from esm.sh or unpkg or directly from a GitHub repo for a one-off script (for example). To do this I created a custom ESBuild plugin to handle HTTP imports - that worked for ,js files. To support running both ESM and CJS, I use tsx.
-
What is your must have npm package on any given project?
I prefer tsx honestly. Nodemon will detect that your using TypeScript and switch from node to ts-node but tsx is a no config necessary version of ts-node that also runs faster. Of course you can configure ts-node to use swc to be faster but then you're playing with config files to get things working.
-
Question about debugging TypeScript
I highly recommend you give this a shot over ts-node
-
Jsx as a general templating language?
Dude I just worked on a PoC a few hours ago. What I did was use ReactDOM's renderToStaticMarkup and tsx to execute the script so I get jsx transpilation on the fly.
-
Thoughts about Deno?
I’ve been trying to adopt Deno into new projects, but I find Node through tsx good enough.
-
Will nodeJs ever have out of the box typescript support?
try tsx. it has support for watch mode and works great with esm module projects.
-
Why is this so hard to do? Help
This is the answer: https://github.com/esbuild-kit/tsx
-
<3 Deno
Have a look at https://github.com/esbuild-kit/tsx
_tsx is a CLI command (alternative to node) for seamlessly running TypeScript & ESM, in both commonjs & module package types.
It's powered by esbuild so it's insanely fast._
What are some alternatives?
ts-monorepo - Template for setting up a TypeScript monorepo
esbuild-runner - ⚡️ Super-fast on-the-fly transpilation of modern JS, TypeScript and JSX using esbuild
storybook - Storybook is a frontend workshop for building UI components and pages in isolation. Made for UI development, testing, and documentation.
ts-node - TypeScript execution and REPL for node.js
babel-plugin-tsconfig-paths-module-resolver - Use tsconfig-paths in any bundler that supports a custom babel config.
ts-runtime-comparison - Comparison of Node.js TypeScript runtimes
Visual Studio Code - Visual Studio Code
esno - Alias to `tsx`
ts-monorepo-absolute-import-paths - A bare-bones Typescript/Node.js starter template with Absolute Path imports, Incremental Compilation and Live-Reloading built it.
esbuild-node-tsc - Build your Typescript Node.js projects using blazing fast esbuild
tsconfig-applier - Welcome to `tsconfig-applier`! This Visual Studio Code extension simplifies the process of selecting and applying TypeScript configuration files (`tsconfig.json`) from the https://github.com/tsconfig/bases repository. With this extension, you can effortlessly browse through available configuration
vite - Next generation frontend tooling. It's fast!