зеркало из https://github.com/microsoft/rnx-kit.git
e25358660a
* Breaking-change update to config package:
(1) Only search for rnx-kit configuration in package.json. We no longer search for config in places like rnx-kit.config.js (e.g. no more cosmiconfig). Why this change? In all the places we use rnx-kit internally, no one is using this mechanism. Further, in external forums, there have been general complaints about JS devs having to manage too many config files -- package.json is the preferred single source. It didn't seem worth it to continue carrying comsmiconfig as a dependency, since we aren't using it.
(2) Remove defaults from the config package. They are going into the CLI where they can be conditionally defined based on variables like the current platform. This is needed for bundleOutput. As a result, all config is now optional.
(3) Function that get bundle and server config now validate input and fail accordingly.
(4) Server config can now be absent when bundling is enabled, and it will default to using the bundle configuration. This is a convenience, and will help devs avoid duplicating config between bundle and server props.
(5) Introduce TypeScriptValidationOptions to give fine-grained control over how TS checking behaves.
(6) Align bundling properties with RN CLI names. Add: bundleOutput. Remove: distPath. Rename: entryPath -> entryFile, sourceMapPath -> sourcemapOutput, sourceMapSourcesRootPath -> sourcemapSourcesRoot, assetsPath -> assetsDest.
(7) Remove support for deprecated property experimental_treeShake.
(8) Add helpful errors when accessing removed properties. This is to assist devs who upgrade across the breaking version change without fixing up all areas of their code that are impacted.
* docs(changeset): Breaking-change update to config package:(1) Only search for rnx-kit configuration in package.json. We no longer search for config in places like rnx-kit.config.js (e.g. no more cosmiconfig). Why this change? In all the places we use rnx-kit internally, no one is using this mechanism. Further, in external forums, there have been general complaints about JS devs having to manage too many config files -- package.json is the preferred single source. It didn't seem worth it to continue carrying comsmiconfig as a dependency, since we aren't using it.(2) Remove defaults from the config package. They are going into the CLI where they can be conditionally defined based on variables like the current platform. This is needed for bundleOutput. As a result, all config is now optional.(3) Function that get bundle and server config now validate input and fail accordingly.(4) Server config can now be absent when bundling is enabled, and it will default to using the bundle configuration. This is a convenience, and will
* Update change file to be more descriptive about the breaking changes going into @rnx-kit/config.
* Manually update package version while keeping changelog entry
* Change bundle definition to bundle config. Stop throwing exceptions and instead return undefined.
* Final updates to config package. Includes doc updates and comment updates.
* update config package changeset entry
* fix config package changeset file
* Remove defaults from server config
* cli update
* reorder params for TPN
* update changeset descriptions
* fix aar tests
* Update bundling guide and cli/config READMEs. Update test-app to use new CLI/config packages.
* fix typos
* tweaks after a final read-through
* fixes
* update bundling guide
* Remove unnecessary getServerConfig API. Make server use bundle config when server config is not present. On server, never use tree shaking.
* Update metro version to align with other packages
* remove + from command-line for windows runs
* fix changelog file
* pr feedback
* pr feedback
* pr feedback
* RELEASING: Releasing 3 package(s)
Releases:
@rnx-kit/cli@0.14.0
@rnx-kit/metro-service@2.0.0
@rnx-kit/config@0.5.0
* revert manual version updates
* Revert "RELEASING: Releasing 3 package(s)"
This reverts commit
|
||
|---|---|---|
| .. | ||
| img | ||
| .nojekyll | ||