Static assets

Static assets, like fonts or images, need be be included in your output directory so that they can be served by luna-js.

Inside your luna.config.js, you can define an array of assets which will be copied inside your public directory on build time.

assets: {
    // A configuration object for static resources (images, fonts, ...)
    static: {
        // An array of copy tasks
        sources: [ {
            input: "assets/images/**/*", output: "assets/images"
        } ]
    }
}

Using static assets

If you ever plan to host your static assets on another domain as luna-js, you should use the asset helper of the global luna object.

export default () => {
    return `
        <img src="${luna.asset("/assets/img/example-image.png")}" alt="An example image" />
    `;
}

The luna object is available globally inside the server context of your luna-js application. No need to import anything. In the client context, the same luna object is available on the window.

Setting a different asset domain

To set a different asset domain, you can change the context and domain properties inside the assets section of your luna.config.js.

{
    assets: {
        domain: "<url-to-a-static-file-hoster>"
        context: "<optional-context-path>"
    }
}

Your complete public folder should be uploaded to the different host or be available under the specified context.