angular/integration/ng_elements/package.json

{
  "name": "angular-integration",
  "version": "0.0.0",
  "license": "MIT",
  "dependencies": {
    "@angular/common": "link:./in-existing-linked-by-bazel",
    "@angular/compiler": "link:./in-existing-linked-by-bazel",
    "@angular/compiler-cli": "link:./in-existing-linked-by-bazel",
    "@angular/core": "link:./in-existing-linked-by-bazel",
    "@angular/elements": "link:./in-existing-linked-by-bazel",
    "@angular/platform-browser": "link:./in-existing-linked-by-bazel",
    "rxjs": "^7.0.0",
    "tslib": "^2.3.0",
    "typescript": "5.9.3",
    "zone.js": "0.16.0"
  },
  "devDependencies": {
    "@babel/core": "7.29.0",
    "@rollup/plugin-babel": "^6.0.0",
    "@rollup/plugin-node-resolve": "^16.0.0",
    "@types/jasmine": "^6.0.0",
    "@types/jasminewd2": "^2.0.8",
    "concurrently": "9.2.1",
    "lite-server": "2.6.1",
    "protractor": "^7.0.0",
    "rollup": "4.57.1"
  },
  "scripts": {
    "build": "pnpm ngc && pnpm rollup -c rollup.config.mjs",
    "test": "pnpm build && concurrently \"pnpm run serve\" \"pnpm run protractor\" --kill-others --success first",
    "serve": "lite-server -c e2e/browser.config.json",
    "preprotractor": "tsc -p e2e",
    "protractor": "protractor e2e/protractor.config.js"
  },
  "private": true,
  "packageManager": "pnpm@10.33.0"
}
test(elements): add basic integration test for angular elements (#24861) PR Close #24861 2018-07-15 23:02:16 +00:00			`{`
			`"name": "angular-integration",`
			`"version": "0.0.0",`
			`"license": "MIT",`
			`"dependencies": {`
test: update integration test dependencies (#63937) During a previous PR review, it was noted that the `next` tag was causing confusion. This commit updates the dependencies for the integration tests to resolve this ambiguity and ensure clarity going forward. Additionally, this change uses the `link:` protocol to ensure that `pnpm i` does not fail when lockfiles or dependencies are updated outside of Bazel. PR Close #63937 2025-09-19 11:57:36 +00:00			`"@angular/common": "link:./in-existing-linked-by-bazel",`
			`"@angular/compiler": "link:./in-existing-linked-by-bazel",`
			`"@angular/compiler-cli": "link:./in-existing-linked-by-bazel",`
			`"@angular/core": "link:./in-existing-linked-by-bazel",`
			`"@angular/elements": "link:./in-existing-linked-by-bazel",`
			`"@angular/platform-browser": "link:./in-existing-linked-by-bazel",`
build: remove yarn from integration tests, switch to pnpm (#63902) This commit removes Yarn as a package manager for integration tests and migrates to pnpm. This change aims to standardize package management across the project, leveraging pnpm's efficiency and consistent behavior for dependency resolution and installation. PR Close #63902 2025-09-18 09:46:02 +00:00			`"rxjs": "^7.0.0",`
			`"tslib": "^2.3.0",`
build: update dependency typescript to v5.9.3 (#64207) See associated pull request for more information. Closes #64192 as a pr takeover PR Close #64207 2025-10-02 15:41:17 +00:00			`"typescript": "5.9.3",`
build: update all non-major dependencies See associated pull request for more information. 2025-11-26 09:10:24 +00:00			`"zone.js": "0.16.0"`
test(elements): add basic integration test for angular elements (#24861) PR Close #24861 2018-07-15 23:02:16 +00:00			`},`
			`"devDependencies": {`
build: update all non-major dependencies See associated pull request for more information. 2026-02-06 16:51:45 +00:00			`"@babel/core": "7.29.0",`
build: remove yarn from integration tests, switch to pnpm (#63902) This commit removes Yarn as a package manager for integration tests and migrates to pnpm. This change aims to standardize package management across the project, leveraging pnpm's efficiency and consistent behavior for dependency resolution and installation. PR Close #63902 2025-09-18 09:46:02 +00:00			`"@rollup/plugin-babel": "^6.0.0",`
			`"@rollup/plugin-node-resolve": "^16.0.0",`
build: update Jasmine to 6.0.0 Jasmine enables `forbidDuplicateNames: true` by default. So we also need to desambiguate duplicate spec names. 2026-02-04 10:23:04 +00:00			`"@types/jasmine": "^6.0.0",`
build: remove yarn from integration tests, switch to pnpm (#63902) This commit removes Yarn as a package manager for integration tests and migrates to pnpm. This change aims to standardize package management across the project, leveraging pnpm's efficiency and consistent behavior for dependency resolution and installation. PR Close #63902 2025-09-18 09:46:02 +00:00			`"@types/jasminewd2": "^2.0.8",`
build: update dependency concurrently to v9 (#63918) See associated pull request for more information. PR Close #63918 2025-09-19 14:46:40 +00:00			`"concurrently": "9.2.1",`
build: update all non-major dependencies (#63928) See associated pull request for more information. PR Close #63928 2025-09-19 15:08:21 +00:00			`"lite-server": "2.6.1",`
build: remove yarn from integration tests, switch to pnpm (#63902) This commit removes Yarn as a package manager for integration tests and migrates to pnpm. This change aims to standardize package management across the project, leveraging pnpm's efficiency and consistent behavior for dependency resolution and installation. PR Close #63902 2025-09-18 09:46:02 +00:00			`"protractor": "^7.0.0",`
build: update all non-major dependencies See associated pull request for more information. 2026-02-06 16:51:45 +00:00			`"rollup": "4.57.1"`
test: use puppeteer in integration tests and to download correct chromedriver (#35049) This means integration tests no longer need to depend on a $CI_CHROMEDRIVER_VERSION_ARG environment variable to specify which chromedriver version to download to match the locally installed chrome. This was bad DX and not having it specified was not reliable as webdriver-manager would not always download the chromedriver version to work with the locally installed chrome. webdriver-manager update --gecko=false --standalone=false $CI_CHROMEDRIVER_VERSION_ARG is now replaced with node webdriver-manager-update.js in the root package.json, which checks which version of chrome puppeteer has come bundled with & downloads informs webdriver-manager to download the corresponding chrome driver version. Integration tests now use "webdriver-manager": "file:../../node_modules/webdriver-manager" so they don't have to waste time calling webdriver-manager update in postinstall "// resolutions": "Ensure a single version of webdriver-manager which comes from root node_modules that has already run webdriver-manager update", "resolutions": { "**/webdriver-manager": "file:../../node_modules/webdriver-manager" } This should speed up each integration postinstall by a few seconds. Further, integration test package.json files link puppeteer via file:../../node_modules/puppeteer which is the ideal situation as the puppeteer post-install won't download chrome if it is already downloaded. In CI, since node_modules is cached it should not need to download Chrome either unless the node_modules cache is busted. NB: each version of puppeteer comes bundles with a specific version of chrome. Root package.json & yarn.lock currently pull down puppeteer 2.1.0 which comes with chrome 80. See https://github.com/puppeteer/puppeteer#q-which-chromium-version-does-puppeteer-use for more info. Only two references to CI_CHROMEDRIVER_VERSION_ARG left in integration tests at integration/bazel-schematics/test.sh which I'm not entirely sure how to get rid of it Use a lightweight puppeteer=>chrome version mapping instead of launching chrome and calling browser.version() Launching puppeteer headless chrome and calling browser.version() was a heavy-handed approach to determine the Chrome version. A small and easy to update mappings file is a better solution and it means that the `yarn install` step does not require chrome shared libs available on the system for its postinstall step PR Close #35049 2020-01-31 23:50:44 +00:00			`},`
test(elements): add basic integration test for angular elements (#24861) PR Close #24861 2018-07-15 23:02:16 +00:00			`"scripts": {`
build: remove yarn from integration tests, switch to pnpm (#63902) This commit removes Yarn as a package manager for integration tests and migrates to pnpm. This change aims to standardize package management across the project, leveraging pnpm's efficiency and consistent behavior for dependency resolution and installation. PR Close #63902 2025-09-18 09:46:02 +00:00			`"build": "pnpm ngc && pnpm rollup -c rollup.config.mjs",`
			`"test": "pnpm build && concurrently \"pnpm run serve\" \"pnpm run protractor\" --kill-others --success first",`
test(elements): add basic integration test for angular elements (#24861) PR Close #24861 2018-07-15 23:02:16 +00:00			`"serve": "lite-server -c e2e/browser.config.json",`
			`"preprotractor": "tsc -p e2e",`
			`"protractor": "protractor e2e/protractor.config.js"`
feat(elements): enable Shadow DOM v1 and slots (#24861) When using ViewEncapsulation.ShadowDom, Angular will not remove the child nodes of the DOM node a root Component is bootstrapped into. This enables developers building Angular Elements to use the `<slot>` element to do native content projection. PR Close #24861 2018-07-16 01:53:18 +00:00			`},`
build: remove yarn from integration tests, switch to pnpm (#63902) This commit removes Yarn as a package manager for integration tests and migrates to pnpm. This change aims to standardize package management across the project, leveraging pnpm's efficiency and consistent behavior for dependency resolution and installation. PR Close #63902 2025-09-18 09:46:02 +00:00			`"private": true,`
build: update pnpm to v10.33.0 See associated pull request for more information. 2026-03-27 06:07:45 +00:00			`"packageManager": "pnpm@10.33.0"`
test: update integration test dependencies (#63937) During a previous PR review, it was noted that the `next` tag was causing confusion. This commit updates the dependencies for the integration tests to resolve this ambiguity and ensure clarity going forward. Additionally, this change uses the `link:` protocol to ensure that `pnpm i` does not fail when lockfiles or dependencies are updated outside of Bazel. PR Close #63937 2025-09-19 11:57:36 +00:00			`}`