Challenges processing JavaScript as custom template format

[greatislander]

Hello,

I've been working on using esbuild to bundle JavaScript assets for an Eleventy site via a custom template format. As the site uses *.11tydata.js files, I need to make sure that they aren't processed as templates. I've tried skipping these templates from inside the compile function (as demonstrated here) and also by using the compileOptions.permalink option (as demonstrated here). However, Eleventy still tries to process an *.11tydata.js file as a template if that file attempts to define a permalink within eleventyComputed. My guess is that the compile skip logic and compileOptions.permalink logic are superseded by the permalink in the computed data which causes Eleventy to try to render the *.11tydata.js file. I've created a minimal reproduction of the issue here:

https://github.com/greatislander/js-template-format

To see what I mean, you can clone this repository and run npm run debug. Then comment out this line and try again. In the first instance the build fails and you can see that Eleventy is treating the JavaScript data file as a template, while in the second instance the build succeeds.

Any insights on how to avoid this issue would be greatly appreciated!