feat(dts): transform vue script setup if no type-only macros

[yusufkandemir]

🔗 Linked issue

Resolves #209

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Some macros in <script setup> have a type-only variant:

• defineProps
• defineEmits
• defineSlots
• defineModel

As long as their type-only variant is NOT used, they can safely be transformed into JS. So, this PR improves the exclusion logic to exclude <script setup> only if the file contains some type-only macro usage.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[danielroe]

Would you be able to look at the failing test? 🙏

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.50%. Comparing base (9000888) to head (a4eb997).
Report is 50 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #210      +/-   ##
==========================================
- Coverage   82.86%   74.50%   -8.37%     
==========================================
  Files          12       12              
  Lines         852      753      -99     
  Branches      133      147      +14     
==========================================
- Hits          706      561     -145     
- Misses        144      190      +46     
  Partials        2        2              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[danielroe]

Perhaps we could use strip-literal?

[yusufkandemir]

I am not sure if that would increase the accuracy. But, it will be slower as it will have to parse the whole document first.

So, if performance is not really a concern and/or accuracy is more important, then I think using js-tokens would be better. strip-literal uses js-tokens to filter the comment and literal related stuff. We would use it to check for identifiers(the macro names in this case). Since it's iterator-based, we won't have to parse the whole document when there is a macro. So, it will be better in terms of performance compared to strip-literal. It would also simplify the code as we would no longer need regexes.

Please let me know if we should keep it like this or go with the js-tokens approach.

[danielroe]

sure - let's use js-tokens then!

[yusufkandemir]

Done 👍 Just to give a rough statistic, executing the exclude method went from ~0.1ms to ~1ms on my machine(Apple M1).