You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before I converted to using dts-cls, I was using tsdx. When I ran the build command it transpiled all of the CJS into the same directory structure as the source, along side the types.
Now with the dts-cli, the transpiled CJS is only ever rolled up and not output to the same directory structure where as the types are still being done in the hierarchy.
Our library has users that want to access elements of the library directly, including elements that aren't published directly to the main index.js file. So now they cannot access those elements
Expected behavior
dts-cli generates the same directory structure as tsdx did
Suggested solution(s)
I tried the --entries src/**/*.ts hoping that it would do the transpiling to each file but that did not work
if don't want to bundle, so why not using tsc directly?
also, IMHO, it's not a good practice to import something like my-awesome-lib/dist/foo.js - it's not a public api, and be likely to be changed in any releases (even in patch). I'd suggest put all the exported things in a index.js.
Current Behavior
Before I converted to using dts-cls, I was using tsdx. When I ran the build command it transpiled all of the CJS into the same directory structure as the source, along side the types.
Now with the dts-cli, the transpiled CJS is only ever rolled up and not output to the same directory structure where as the types are still being done in the hierarchy.
Our library has users that want to access elements of the library directly, including elements that aren't published directly to the main
index.js
file. So now they cannot access those elementsExpected behavior
dts-cli generates the same directory structure as tsdx did
Suggested solution(s)
I tried the
--entries src/**/*.ts
hoping that it would do the transpiling to each file but that did not workAdditional context
Your environment
The text was updated successfully, but these errors were encountered: