fix: package exports using api extractor #169
Draft
+89
−91
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR using latest
vite-plugin-dts
and using@microsoft/api-extractor
(rollupTypes: true
) to generate only 1 dts, 1 js and 1 cjs files.Right now WebStorm/IntelliJ intellisense not working, VSCode autocompletion working fine.
We will need to add some stuff in the build for JetBrains IDE.
NOTE: missing
three
andpostprocessing
dependencies in the plyaground, it is working fine, no need to change anything in the sfc files.Looks like latest dts plugin will require moving script lang stuff to sfc script, some components will require to create a ts module since it is exporting some symbols (for example EffectComposer sfc) and sfc script cannot export ts modules (no idea if it will fail on build time, the error comes from eslint):
ESLint error
Without changing
Pixelation sfc
, VSCode not showing auto completion, you can revert the changes, rebuild the package and the tgz and use this playground: https://github.com/userquin/tresjs-post-processing-playgroundFrom this PR from root folder:
nr build && pnpm pack
then in the playground