Possible to avoid specifying every file?

[timreichen]

Possible to avoid specifying every file?

[timreichen]

I don't quite understand that use case. Bundler needs entry files specified, else it does not know which files to bundle up. Do you mean to transpile/transform all files in a dir instead of bundling?

[ebebbington]

I don't quite understand that use case. Bundler needs entry files specified, else it does not know which files to bundle up. Do you mean to transpile/transform all files in a dir instead of bundling?

Yeah pretty much, so instead of having to do:

$ bundler bundle src/js/home.ts=dist/js/home.js src/js/call.ts=dist/js/call.js # annd maybe 10 more files

You could do:

$ bundler bundle src/js=dist/js

[timreichen]

That is an interesting use case. Though it kinda pervents what bundler is meant to do doesn‘t it? Why would you want to do that instead of bundling?
I don‘t like magic path resolutions so I think I won’t implement it like that. But I guess that could be achieved by a simple script that collects all paths recursively and then call the bundler command.

[ebebbington]

I guess it just saves having a command that could be upwards of 100-200 characters long to specify every file (as opposed to using an entrypoint)

I mean it's no biggie, the again, you (as in thee user) could just store the command in a Makefile and reuse it from there 🤔

[timreichen]

No I mean, why would you even want to have so many files as entry files? In what use case would that be practical?

[ebebbington]

Take https://github/Okku/destiny as an example, they plan on moving to Deno, but compile all their source code into a dist directory, with the dist dir mirroring src

[timreichen]

Is there an advantage on a mirrored dist dir over a flattened one? I am currently working on the next iteration of bundler, so if there is I might want to consider it.

[alfredosalzillo]

@timreichen mirroring the src folder can be useful to bundle modular libraries

[timreichen]

@alfredosalzillo how do you mean?

[timreichen]

Closing due to inactivity. Feel free to reopen.

[ebebbington]

Is there an advantage on a mirrored dist dir over a flattened one? I am currently working on the next iteration of bundler, so if there is I might want to consider it.

Not necessarily, it's more about the bundle result not being a single file, if every file was bundled individually, I could still link to my page specific js files eg <script src="/assets/pagejs/users/new.js">

Though as it stands, it seems like I'd have to handle some kind of routing in the app.ts (entrypoint to bundle), so when I do link the bundled file in my views, js related. to other pages wont run, for example:

import UserNewPageJS from "./users/new"
import UserIndexPageJS from "./users/index"
import HeaderPageJS from "./header"

if (window.location.href === "/users/new")
  UserNewPageJS.init() // just initiates the DOM event listeners
if (window.location.href === "users")
  ... // same as above
  
HeaderPageJS.init()

[timreichen]

@ebebbington I guess that is slightly missing the goal of this project. bundler should, well, bundle files together to make webpage download as fast as possible. Maybe dynamic imports can solve the problem?

import HeaderPageJS from "./header.ts"

if (window.location.href === "/users/new")
await import("./users/new.ts")
if (window.location.href === "users")
await import("./users/index.ts")
HeaderPageJS.init()