-
Notifications
You must be signed in to change notification settings - Fork 11.9k
No way to access compilation output files #27386
Copy link
Copy link
Open
Labels
angular/build:applicationarea: @angular/buildfeatureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under considerationFeature request for which voting has completed and the request is now under considerationfreq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarely
Metadata
Metadata
Assignees
Labels
angular/build:applicationarea: @angular/buildfeatureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under considerationFeature request for which voting has completed and the request is now under considerationfreq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarely
Command
build, serve
Description
I have an esbuild plugin that is resposible to collect outputFiles after compilation (using
onEndhook withresult.outputFiles).When using application builder (esbuild) with custom plugins there is no way to access full list of outputFiles, only those emitted by
mainentrypoint compilation. There is no way to access additional files emited by angular builder, such aspolyfills, assets, styles etc.Previously, with using webpack plugin, i was able to get full list of outputFiles by using
processAssetscompilation hook.I need to list emited files, as this is only way to get full names with filenames hash.
MY point is to build something like manifest of compilation result output files.
Describe the solution you'd like
I would like to be able to access all compilation files by esbuild plugin.
Describe alternatives you've considered
An alternative could be to access output files as an result of builder output, currently
buildcommand only returns{success: true}without information about output files.