-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Is it possible to specify the AMD module (project) name during compilation? #4027
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
In addition to setting baseurl, I also think something like requirejs route mapping would also be appropriate for TS. |
The current way is to use Filling in the names should be simple assuming you have a |
I think a new flag would be reasonable. It would be nice not to have to use an |
is this for both JS and .d.ts? how about enabling |
That would be fantastic. The ultimate goal is to concat the entire library (both JS and d.ts) into a single file(s) which can be distributed and easily consumed by external users via:
Having the compiler generate the module names would at least make it possible to concat with external tools, but having it handle the total sequence would be awesome! |
this should be fixed then by #5090 |
I have a large library separated into many sub directories and modules which use ES6 module syntax. They are arranged on disk something like this:
Instead of generating anonymous AMD modules and declaration files, I'd like to be able to specify a root path name and have the output explicitly define the module names, so that the files can be easily concatenated and minified:
foo.js
foo.d.ts
Is there a way to do this with the current compiler flags or tsconfig?
The text was updated successfully, but these errors were encountered: