Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
angular/packages/compiler-cli/esbuild.config.js

21 lines
600 B
JavaScript
Raw Normal View History

refactor: setup bundling for `@angular/compiler-cli` package (#43431) All other frameworks packages are now using APF v13 and are strict ESM packages. The compiler-cli does not use APF and is currently shipped with its devmode ES5 CommonJS sources. This is problematic as CommonJS cannot simply import from ECMAScript modules (like `@angular/compiler`). To fix this we use a bundler that allows us to ship the compiler-cli as a strict ESM package. Note: An ESM can import from an ESM without any problems. This is what we need hre. Unfortunatley we need a bundler here because converting the compiler-cli to ESM is non-trivial as relative imports would need an explicit `.js` extension. This work can be simplified by using a bundler that avoids relative imports completely. Note: This commit uses code-splitting to create multiple bundle entry-points for `yarn ngc, `yarn ngcc` etc. This commit removed the old `ivy-ngcc` entry-point that just printed an error message (to reduce amount of bundles having to be configured). PR Close #43431
2021-09-27 23:17:43 +00: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
*/
module.exports = {
refactor: remove `__ESM_IMPORT_META_URL__` workaround now that we can use ESM (#48521) The `__ESM_IMPORT_META_URL__` trick was used because we used both ESM and CommonJS in this repo. It was an interop needed because `import.meta.url` syntax couldn't be used as it woud have caused syntax errors. We still need to keep the CommonJS/ESM interop in the compiler-cli because g3 relies on the compiler and uses CommonJS. This affects very few places, just in the compiler- so this is acceptable. PR Close #48521
2022-12-07 16:16:04 +00:00
resolveExtensions : ['.mjs', '.js'],
refactor: setup bundling for `@angular/compiler-cli` package (#43431) All other frameworks packages are now using APF v13 and are strict ESM packages. The compiler-cli does not use APF and is currently shipped with its devmode ES5 CommonJS sources. This is problematic as CommonJS cannot simply import from ECMAScript modules (like `@angular/compiler`). To fix this we use a bundler that allows us to ship the compiler-cli as a strict ESM package. Note: An ESM can import from an ESM without any problems. This is what we need hre. Unfortunatley we need a bundler here because converting the compiler-cli to ESM is non-trivial as relative imports would need an explicit `.js` extension. This work can be simplified by using a bundler that avoids relative imports completely. Note: This commit uses code-splitting to create multiple bundle entry-points for `yarn ngc, `yarn ngcc` etc. This commit removed the old `ivy-ngcc` entry-point that just printed an error message (to reduce amount of bundles having to be configured). PR Close #43431
2021-09-27 23:17:43 +00:00
// Note: `@bazel/esbuild` has a bug and does not pass-through the format from Starlark.
refactor: remove `__ESM_IMPORT_META_URL__` workaround now that we can use ESM (#48521) The `__ESM_IMPORT_META_URL__` trick was used because we used both ESM and CommonJS in this repo. It was an interop needed because `import.meta.url` syntax couldn't be used as it woud have caused syntax errors. We still need to keep the CommonJS/ESM interop in the compiler-cli because g3 relies on the compiler and uses CommonJS. This affects very few places, just in the compiler- so this is acceptable. PR Close #48521
2022-12-07 16:16:04 +00:00
format : 'esm',
banner : {
refactor: setup bundling for `@angular/compiler-cli` package (#43431) All other frameworks packages are now using APF v13 and are strict ESM packages. The compiler-cli does not use APF and is currently shipped with its devmode ES5 CommonJS sources. This is problematic as CommonJS cannot simply import from ECMAScript modules (like `@angular/compiler`). To fix this we use a bundler that allows us to ship the compiler-cli as a strict ESM package. Note: An ESM can import from an ESM without any problems. This is what we need hre. Unfortunatley we need a bundler here because converting the compiler-cli to ESM is non-trivial as relative imports would need an explicit `.js` extension. This work can be simplified by using a bundler that avoids relative imports completely. Note: This commit uses code-splitting to create multiple bundle entry-points for `yarn ngc, `yarn ngcc` etc. This commit removed the old `ivy-ngcc` entry-point that just printed an error message (to reduce amount of bundles having to be configured). PR Close #43431
2021-09-27 23:17:43 +00:00
// Workaround for: https://github.com/evanw/esbuild/issues/946
refactor: remove `__ESM_IMPORT_META_URL__` workaround now that we can use ESM (#48521) The `__ESM_IMPORT_META_URL__` trick was used because we used both ESM and CommonJS in this repo. It was an interop needed because `import.meta.url` syntax couldn't be used as it woud have caused syntax errors. We still need to keep the CommonJS/ESM interop in the compiler-cli because g3 relies on the compiler and uses CommonJS. This affects very few places, just in the compiler- so this is acceptable. PR Close #48521
2022-12-07 16:16:04 +00:00
js : `
refactor: setup bundling for `@angular/compiler-cli` package (#43431) All other frameworks packages are now using APF v13 and are strict ESM packages. The compiler-cli does not use APF and is currently shipped with its devmode ES5 CommonJS sources. This is problematic as CommonJS cannot simply import from ECMAScript modules (like `@angular/compiler`). To fix this we use a bundler that allows us to ship the compiler-cli as a strict ESM package. Note: An ESM can import from an ESM without any problems. This is what we need hre. Unfortunatley we need a bundler here because converting the compiler-cli to ESM is non-trivial as relative imports would need an explicit `.js` extension. This work can be simplified by using a bundler that avoids relative imports completely. Note: This commit uses code-splitting to create multiple bundle entry-points for `yarn ngc, `yarn ngcc` etc. This commit removed the old `ivy-ngcc` entry-point that just printed an error message (to reduce amount of bundles having to be configured). PR Close #43431
2021-09-27 23:17:43 +00:00
import {createRequire as __cjsCompatRequire} from 'module';
const require = __cjsCompatRequire(import.meta.url);
`,
},
};
Reference in a new issue Copy permalink