Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--filter and --force don't work #18

Open
wakecoder opened this issue Sep 26, 2018 · 3 comments
Open

--filter and --force don't work #18

wakecoder opened this issue Sep 26, 2018 · 3 comments

Comments

@wakecoder
Copy link

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.

@vennekilde
Copy link

vennekilde commented Aug 13, 2019

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

@tgouala
Copy link

tgouala commented Jun 14, 2020

I have the same problem here. It makes it hard to use the tool in a CI. This issue is quite old, is there any plan to fix it or workaround ? Thanks !

@tgouala
Copy link

tgouala commented Jun 14, 2020

Just find out -f works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants