-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
integration with SSG? #74
Comments
That's an interesting question. You could indeed try to point to your 11ty generated index.html using the {{#each assets.css}}
<link rel="stylesheet" href='{{{.}}}' />
{{/each}}
{{#if assets.runtime}}
<script type='text/javascript'>
{{{assets.runtime}}}
</script>
{{/if}}
{{#each assets.js}}
<script type='text/javascript' src='{{{.}}}' async></script>
{{/each}} ^ This is taken from the default template. Alternatively, what jetpack does behind the scenes is it reads Lines 207 to 251 in bd5e84e
|
Cool beans. Glad to hear it's unlikely I'll need to do custom webpack stuff anymore. While it might take a while before I have time to convert from my custom stuff to using jetpack with one of the configurations you propose above, I'm closing this now. as I'm confident enough now, based on what you've shown, that I will be able to migrate to jetpack at some point soon. |
Hi, my SPA is primarily showing/hiding/enabling/disabling bits of pre-generated html, which I'm generating with 11ty. Would jetpack be able to use my generated index.html as the template for including the bundle(s) or would I be better off just including references to them in the templates which build my index.html or do custom webpack stuff rather than jetpack?
The text was updated successfully, but these errors were encountered: