devtools/tools/esbuild/esbuild-iife.config.mjs

/**
 * @license
 * Copyright Google LLC All Rights Reserved.
 *
 * Use of this source code is governed by an MIT-style license that can be
 * found in the LICENSE file at https://angular.io/license
 */

import createConfig from './esbuild-base.config.mjs';

export default {
  ...(await createConfig({enableLinker: false, optimize: false})),
  format: 'iife',
};
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages. 2021-12-16 02:00:43 -05:00			`/**`
			`* @license`
			`* Copyright Google LLC All Rights Reserved.`
			`*`
			`* Use of this source code is governed by an MIT-style license that can be`
			`* found in the LICENSE file at https://angular.io/license`
			`*/`

refactor: simplify devtools setup given recent ESM changes (#48521) Since the `defaults.bzl` repo-wide macros are now supporting ESM, the special spec-bundle logic from `devtools` can be removed. Also the esbuild configurations need to be updated to account for the recent dev-infra build-tooling changes. Also properly now ensures that `aysnc/await` is downleveled for ZoneJS compatibility. PR Close #48521 2022-12-14 10:38:17 +00:00			`import createConfig from './esbuild-base.config.mjs';`
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages. 2021-12-16 02:00:43 -05:00
			`export default {`
build(devtools): fix issue where esbuild configs were not being set properly in DevTools (#48762) Previously, a createConfig helper function was created to consolidate common esbuild configurations for DevTools. This function is asynchronous, but when it was used to set the configuration in various esbuild config files, it was used as if it was synchronous. This commit fixes this issue by wrapping the output of the function in await, so that it propagates the configurations to esbuild correctly. PR Close #48762 2023-01-18 03:50:33 -05:00			`...(await createConfig({enableLinker: false, optimize: false})),`
refactor: simplify devtools setup given recent ESM changes (#48521) Since the `defaults.bzl` repo-wide macros are now supporting ESM, the special spec-bundle logic from `devtools` can be removed. Also the esbuild configurations need to be updated to account for the recent dev-infra build-tooling changes. Also properly now ensures that `aysnc/await` is downleveled for ZoneJS compatibility. PR Close #48521 2022-12-14 10:38:17 +00:00			`format: 'iife',`
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages. 2021-12-16 02:00:43 -05:00			`};`