Export jinja files as TS module at build time #1296
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR should fix https://github.com/huggingface-internal/moon-landing/pull/13013. It partially removes the structure introduced in #1255.
Current problem is that inference snippets are generated in the front-end. Since front-end cannot access file-system and therefore the jinja files, we have to find a workaround. This PR adds a build step which exports all jinja files into a single TS module. I've updated the
package.json
file so that now the snippets code should be available in any environment (both node and browser).cc @coyotte508 who suggested such a solution.
Tested it in
@tasks-gen
and "it works"For the record, the exported file (not committed in this PR) looks like this:
# packages/inference/src/snippets/templates.exported.ts