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
On a new Angular 17 project with esbuild compilation pipeline (the default one) with import-meta-env configured with a compile-time transformMode, executing the command env DEBUG_IMPORT_META_ENV="true" NAME="Toto" ng build should inject Toto inside the output javascript Angular file, but the output file still contains the non-transformed code :
Since Angular 17, esbuild has been added as a choice for the compilation pipeline . Webpack can still be used but esbuild is now the default choice for new angular apps. When import-meta-env is added to an esbuild project, it seems that compile-time transforms are not executed anymore.
When enabling verbose logs (by setting the DEBUG_IMPORT_META_ENV to anything), the output of the ng build command shows that import-meta-env is loaded, but the transform function is not called at all.
A little bit of debugging seems to indicate that the issue comes from the fact that build2.onLoad is not called in unplugin, therefore not triggering any transform.
As stated in the ESbuild doc, the onload is only executed if no other plugin handle it
all onLoad callbacks from all plugins will be run in the order they were registered until one takes responsibility for loading the module.
I suspect that Angular register his own plugin, preventing the unplugin one to be called.
Since the ESBuild is quite new, there are not that much configuration examples available online. It could be a simple configuration error on my side. To reproduce this issue, I had to :
create a new Angular 17 project
added multiple NPM packages :
@angular-builders/custom-esbuild to be able to customize the pipeline
dotenv (maybe not needed but I wanted to stick to your documentation)
@import-meta-env/unplugin obviously
@import-meta-env/typescript
modified the angular.json file to use the @angular-builders/custom-esbuild:application builder, and added a new plugin entry (eg. "plugins": ["importMetaEnvPlugin.ts"],)
this last file has the following content (insipred by your documentation and the @angular-builders/custom-esbuild one) :
import type { Plugin } from 'esbuild';
import * as importMetaEnv from "@import-meta-env/unplugin";
const plugin : Plugin = importMetaEnv.esbuild({
example:'.env.example',
transformMode:'compile-time'
});
export default plugin;
The text was updated successfully, but these errors were encountered:
Hello,
tldr;
On a new Angular 17 project with esbuild compilation pipeline (the default one) with import-meta-env configured with a compile-time transformMode, executing the command
env DEBUG_IMPORT_META_ENV="true" NAME="Toto" ng build
should injectToto
inside the output javascript Angular file, but the output file still contains the non-transformed code :some more details
Since Angular 17,
esbuild
has been added as a choice for the compilation pipeline . Webpack can still be used but esbuild is now the default choice for new angular apps. Whenimport-meta-env
is added to an esbuild project, it seems thatcompile-time
transforms are not executed anymore.When enabling verbose logs (by setting the
DEBUG_IMPORT_META_ENV
to anything), the output of theng build
command shows thatimport-meta-env
is loaded, but thetransform
function is not called at all.A little bit of debugging seems to indicate that the issue comes from the fact that
build2.onLoad
is not called inunplugin
, therefore not triggering any transform.As stated in the ESbuild doc, the onload is only executed if no other plugin handle it
I suspect that Angular register his own plugin, preventing the unplugin one to be called.
Here is a github repository that reproduce this issue : https://github.com/jcchalte/runtime-meta-env-esbuild-bug
Since the ESBuild is quite new, there are not that much configuration examples available online. It could be a simple configuration error on my side. To reproduce this issue, I had to :
@angular-builders/custom-esbuild
to be able to customize the pipelinedotenv
(maybe not needed but I wanted to stick to your documentation)@import-meta-env/unplugin
obviously@import-meta-env/typescript
angular.json
file to use the@angular-builders/custom-esbuild:application
builder, and added a new plugin entry (eg."plugins": ["importMetaEnvPlugin.ts"],
)this last file has the following content (insipred by your documentation and the @angular-builders/custom-esbuild one) :
The text was updated successfully, but these errors were encountered: