Support multiple entrypoints

[jodosha]

Features

Multiple Entrypoints

Support multiple entrypoints in a Hanami application.
This feature is meant to split the js/css bundles in a way that makes sense for the user application.

Example: If the user wants a login page that doesn't have all the other js/css bundles, they can create an app/assets/javascripts/login/app.js, and Hanami::Assets will bundle it separately as public/assets/login/app-abc123.js.

Stylesheet importing

Import stylesheets by using the @import directive.

Example: From app.css, a user can import reset.css like this: @import 'reset.css'.

Import images from stylesheets

If an image is referenced from a stylesheet, it will be bundled in the destination directory.

Example:

Given a background image, located at app/assets/images/background.jpg, and a stylesheet like the following app/assets/stylesheets/app.css.

body {
  background-image: url('../images/background.jpg');
  # ...
}

Hanami::Assets will bundle the image at: public/assets/background-UU2XY655.jpg and rewrite the background image path of the destination CSS (public/assets/app-X3IVBUS4.css):

body {
  background-image: url('/assets/background-UU2XY655.jpg');
  # ...
}

The image will be part of the Assets Manifest, and Hanami::Assets will calculate the Subresource Integrity (if enabled).

Implementation

The app will recursively search for app.{js,ts,mjs,mts,tsx,jsx} in app/assets/javascripts and slices/*/assets/javascripts.
The matched files will constitute esbuild entrypoints.