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
When running tspath --force it still prompts the user. However, if I run tspath -f it doesn't.
Likewise, when I run tspath --filter="rr" it ignores the filter and still processes .js files. This is important because, by default tspath isn't processing the d.ts files.
Lastly, I noticed the version on NPM is 1.3.7 but github shows 1.3.5. Not sure how this is the case. When I pull down 1.3.5 from github it appears to work correctly with --force and --filter. However, 1.3.7 installed via NPM displays the issues I noted above.
The text was updated successfully, but these errors were encountered:
The problem appears to be the way the project is built
The dist folder contains the newest 1.3.7 source, but it completely ignores it in favor of the dist/src folder, which is a 2 year old version of 1.3.5
When running tspath --force it still prompts the user. However, if I run tspath -f it doesn't.
Likewise, when I run tspath --filter="rr" it ignores the filter and still processes .js files. This is important because, by default tspath isn't processing the d.ts files.
Lastly, I noticed the version on NPM is 1.3.7 but github shows 1.3.5. Not sure how this is the case. When I pull down 1.3.5 from github it appears to work correctly with --force and --filter. However, 1.3.7 installed via NPM displays the issues I noted above.
The text was updated successfully, but these errors were encountered: