-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
bug(tools): migrate-converged-pkg generator issues #24304
Comments
Removing Needs: Backlog review. Looks like an issue for v-build to track and discuss |
Because this issue has not had activity for over 180 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
Because this issue has not had activity for over 180 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
Because this issue has not had activity for over 180 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
This issue has not had activity for over 180 days! We're adding Soft close label and will close it soon for house-keeping purposes. |
keep open |
While migrating all packages to use
start-storybook
I ran into various issues how things are setup. this issues is aggregate of tracking those1. compat packages
tsconfig.lib.json
incorrectly set to:
should be:
2.
*.mock
file glob support*.mock.
file suffix to be used within tests for mocking purposes (react-dialog)incorrectly set to :
tsconfig.lib.json
tsconfig.spec.json
should be:
tsconfig.lib.json
tsconfig.spec.json
3.
.babelrc.json
setuppreset
setup is present it is being overriddenincorrectly set to:
should be:
4. scope
platform:web
types setupplatform:web
should not usenode
global types withintsconfig.lib.json
@fluentui/global-context
us set asplatform:web
but uses internallyglobal
reference - thus needs to havenode
withintypes
which doesn't adhere to our rules.current logic:
topic to discuss: Should we mark these packages rather via
platform:any
and preserve customtypes
config ?Related issues
The text was updated successfully, but these errors were encountered: