chore: dev-env + esm support + non-compiled internal packages #3071
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.
Overview
This change is the start of a refactor to collocate the storybook/playwright environments across the repo (recommended by turbo) into a single development environment (i.e.,
@iot-app-kit/dev-env
). Collocation of the envs provides:In this change, the dashboard storybook/playwright env is used as the basis of
dev-env
. In later changes, react-components and scene-composer stories/playwright tests will be migrated.To build the
dev-env
, the following additional updates were made:node.js
via"type": "module"
setting in every package.dev-env
,data-mocked
, andhelpers
packages. These packages do not require a build step. Their code is built into their consumer's code.Also includes:
type-fest
dependency in react-components. Turns out, we don't have a direct dependency ontype-fest
, yet we are using it. Must be a transitive dependency letting it be imported somehow. Fix was to install it!RecursivePartial
utility type withtype-fest
'sPartialDeep
.Legal
This project is available under the Apache 2.0 License.