Is there a strategy to use when you generate a manifest file and need to reference it in your library that you’re vending?

I’m vending a JS/TS library that generates some asset files (let’s say a list of keywords) and it generates a manifest file along side it. The manifest file knows some additional information about the generated asset files.

I’m currently letting the client define where the manifest file is being generated and ask them to provide the path as an attribute when they call my library.

This is an unnecessary step for the client as they don’t really use the manifest file.

Is there a strategy to hide away this extra step? I’m currently thinking to generate a fake npm package and put the manifest file in it and reference it. It works but it feels very hacky.