`tsup-node` should not mark module alias as external
See original GitHub issueIf you have a path alias like @app/*
configured in tsconfig.json
and run tsup-node
against your files, @app
will be accidentally marked as external, it needs to be fixed here:
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Module Resolution or Import Alias: The Final Guide - Raul Melo
Tired to have weird imports? It's time to learn how can you enable aliases to your imports and let code more organized.
Read more >Webpack resolve.alias does not work with typescript?
This solved my problem: we were using a custom module syntax which defined aliases to files other than index . Renaming the files...
Read more >Typescript – How to solve the problem with unresolved path ...
The actual cause of the issue is that the tsc compiler does not transpiles correctly the path aliases to absolute (real) paths.
Read more >External check for Domain or Domain Alias match - Drupal
BTW, it seems that DomainAliasLoader will give me something of what I want, but it's marked deprecated, so I'd rather not use it....
Read more >Elixir nested modules, imports, and aliases - Cultivate
Nested is really just an alias to the atom :"Elixir. ... Nesting do def outer, do: :outer defmodule Nested do # WILL NOT...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fow now just use the command
tsup
instead.🎉 This issue has been resolved in version 5.9.2 🎉
The release is available on:
Your semantic-release bot 📦🚀