You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Azure SDK for JS repository uses rollup in order to produce browser bundles.
Historically, every package contained its own rollup configuration files when building a browser bundle for testing.
We have an effort in place to share rollup configuration across packages from a common source.
What to do:
Delete rollup.base.config.js and rollup.test.config.js
Run rushx test from the package folder after setting up your environment
Acceptance criteria:
rushx test succeeds
rollup.base.config.js and rollup.test.config.js are removed from the relevant directories
The text was updated successfully, but these errors were encountered:
ghost
added
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Sep 23, 2021
jeremymeng
added
Client
This issue points to a problem in the data-plane of the library.
EngSys
This issue is impacting the engineering system.
labels
Sep 23, 2021
ghost
removed
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Sep 23, 2021
## What
- Fix incorrect logic when suppressing chai's circular dependency warnings
- Move to the common dev-tool configuration where possible
## Why
This is a longstanding issue that we have, where an incorrect logic was copy-pasted to other places. I figured while cleaning this up that any package I touch can just convert over to the shared dev-tool configuration. Where I was unable
to do that, I just fixed this bug to avoid too many changes in one PR.
Fixes#14292Resolves#17818Resolves#17816Resolves#17815Resolves#17814Resolves#17813Resolves#17810
The Azure SDK for JS repository uses rollup in order to produce browser bundles.
Historically, every package contained its own rollup configuration files when building a browser bundle for testing.
We have an effort in place to share rollup configuration across packages from a common source.
What to do:
rollup.base.config.js
androllup.test.config.js
rollup.config.js
to the following:rushx test
from the package folder after setting up your environmentAcceptance criteria:
rushx test
succeedsrollup.base.config.js
androllup.test.config.js
are removed from the relevant directoriesThe text was updated successfully, but these errors were encountered: