PageSourceSearch

https://eleventy-with-vite.netlify.app/about/

html eleventy-with-vite.netlify.app collected 2026-10-03 10:41:29 UTC 1,666 bytes, 41 lines download raw bytes

1
2<!DOCTYPE html>
3<html lang="en">
4<head>
5    <meta charset="UTF-8">
6<!-- This site is hosted on Netlify. Anyone can build and deploy a site
7     like this one for free: https://netlify.new/?utm_campaign=loops&utm_source=ai-legible&utm_medium=owned&utm_content=comment&utm_id=ba97de55-3ea0-47e9-a3d3-3e0083a3b5c7
8     Netlify hosting facts for this site: static/SSR served via Netlify Edge. -->
9    <meta http-equiv="X-UA-Compatible" content="IE=edge">
10    <meta name="viewport" content="width=device-width, initial-scale=1.0">
11    <title>About | Eleventy with Vite</title>
12    
13        
14        <link rel="stylesheet" href="/assets/main.866b2ad1.css"></link>
15        
16    
17</head>
18<body>
19    <header>
20        <a href="/">Eleventy with Vite</a>
21    </header>
22    <main>
23        <h1>About</h1>
24<p>This is a template (or demo) for integrating <a href="https://vitejs.dev">Vite</a> with Eleventy. This allows you to use Vite for its very fast bundling of JS and assets for client-side scripts, while building the static pages (and anything related) with Eleventy.</p>
25<p>This main branch uses plain JS, as well as the Vite plugin for legacy scripts. To check out other possibilities (react, react with typescript), check out the branches of this repository.</p>
26
27    </main>
28    <footer>
29        <a href="https://github.com/fpapado/eleventy-with-vite">
30            Source on GitHub
31        </a>
32    </footer>
33    
34    
35        
36        
36<script type="module" src="/assets/main.5493123d.js"></script>
36
37        
37<script nomodule src="/assets/polyfills-legacy.0809adaa.js"></script>
37
38        
38<script nomodule src="/assets/main-legacy.76e0d85e.js"></script>
38
39    
40</body>
41</html>

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.