Out flag option does not work correctly

[vercel]

Out flag option does not work correctly

[rauchg]

Why not dist/main/ dist/main-es/ dist/api/ dist/api-es/ ?

[rauchg]

I'd be down to discuss -f / --out-file, but I think the idea that can you can treat a directory or a file the same (because the directory can resolve to /index.js) is quite powerful

For example, I spent some time thinking how ncc could use the CLI instead of the JS API for self-hosting.

• We'd rename src/index.js to src/main.js
• We'd make cli.js require (./main). This is important, because main written like that can resolve to both dir and file
• Then we'd export like this:

ncc build src/main -o dist/main
ncc build src/cli -e './main' -o dist/cli

-e is necessary to avoid the CLI bundling the whole thing. Done!

[rauchg]

You should use dist/api and when you require don't use the .js suffix, so that you can support both situations (file or directory with index.js)

This is by design, because some Node programs need to output more side-effects

[rauchg]

That said, we could support --out dist/api.js --single, which would err if >1 outputs, and give you what you want. But is it really that necessary?

[tunnckoCore]

Why not just support --out-dir and --out-file ?

The -o / --output is usually a flag that allows making output file.

edit: Also, i need to have more than one file in that api directory, or even build multiple things to the dist one.

[tunnckoCore]

Currently, I'm using Rollup and the dist structure is the following

dist/index.js
dist/index-es.js
dist/api/index.js
dist/api/index-es.js

Where, the index.jss should be able to load in the browser and index-es are always using ES modules.

[tunnckoCore]

Hm. Maybe.