Skip to content

output.target vs. output.chunkFormat – why not documented properly ? #5917

Closed
@projektorius96

Description

@projektorius96

TL;DR We should know what targets / formats we are dealing with at first glance , not somewhere in the middle of story of nowhere . Please adjust the documentation of webpack , making more digestible bite for "Getting started", webpack considered daunting exactly due to this. I am telling you this as junior-to-mid developer . This is an honest review the contribution of webpack should pay their attention at .


With reference to the titled & what I've found having a look at source code , in my opinion, not very well documented . What I figured out should be properly explained one or the other way, as for an example:

  • output.target ( default:web [if no browserlist installed] | other values) – meant to denote the output (bundle) format ;

NOTE : the target is relatively global configuration , may be overwritten by output.chunkFormat, unless the .chunkFormat() set to false (default) to accept global target configuration !

  • 'output.chunkFormat' (default:false other values: 'array-push' | 'commonjs' | 'module' | ) – by default it listens for global of output.target unless specified other than default value .

In case I have misinterpreted something , please correct me , but with correspondence how things been documented till-up-date, I would not judge myself too much even if mistaken . It's always good to clarify . Thank you .

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions