feat: add exports for experimental components #464
Merged
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.
What
Adds exports for the
experimental
folder, so that when distributing the package it can be accessed directly.Media
Now the experimental components can be accessed like:
Why
To allow to directly access experimental features, without needing to know the internal file structure of the package.
How
typesVersions
field to package.json to override theexperimental
types (so they don't come from the main index.d.ts file)Extra
I'm opening this as a draft PR because the experimental components are not ready to be distributed yet, once we have a first experimental component we can merge this.
I've already tested this approach in several
rc
releases, if you want to try it out as well you can check 2.6.0-rc.8. I've rolled back the version in package.json so that it gets automatically updated by semantic-release once the PR is merged.The linting issues that you see are due to comments in some experimental components, those should be solved as part of the PRs for each component.