|
1
|
<!DOCTYPE html>
|
|
2
|
<html lang="en">
|
|
3
|
<head>
|
|
4
|
<meta charset="utf-8" />
|
|
5
|
<link rel="icon" href="%PUBLIC_URL%/favicon.ico" />
|
|
6
|
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
|
7
|
<meta name="theme-color" content="#000000" />
|
|
8
|
<meta
|
|
9
|
name="description"
|
|
10
|
content="Web site created using create-react-app"
|
|
11
|
/>
|
|
12
|
<link
|
|
13
|
rel="stylesheet"
|
|
14
|
href="https://unpkg.com/leaflet@1.8.0/dist/leaflet.css"
|
|
15
|
integrity="sha512-hoalWLoI8r4UszCkZ5kL8vayOGVae1oxXe/2A4AO6J9+580uKHDO3JdHb7NzwwzK5xr/Fs0W40kiNHxM9vyTtQ=="
|
|
16
|
crossorigin=""
|
|
17
|
/>
|
|
18
|
<link rel="apple-touch-icon" href="%PUBLIC_URL%/logo192.png" />
|
|
19
|
<!--
|
|
20
|
manifest.json provides metadata used when your web app is installed on a
|
|
21
|
user's mobile device or desktop. See https://developers.google.com/web/fundamentals/web-app-manifest/
|
|
22
|
-->
|
|
23
|
<link rel="manifest" href="%PUBLIC_URL%/manifest.json" />
|
|
24
|
<!--
|
|
25
|
Notice the use of %PUBLIC_URL% in the tags above.
|
|
26
|
It will be replaced with the URL of the `public` folder during the build.
|
|
27
|
Only files inside the `public` folder can be referenced from the HTML.
|
|
28
|
|
|
29
|
Unlike "/favicon.ico" or "favicon.ico", "%PUBLIC_URL%/favicon.ico" will
|
|
30
|
work correctly both with client-side routing and a non-root public URL.
|
|
31
|
Learn how to configure a non-root public URL by running `npm run build`.
|
|
32
|
-->
|
|
33
|
<script
|
|
34
|
src="https://unpkg.com/leaflet@1.8.0/dist/leaflet.js"
|
|
35
|
integrity="sha512-BB3hKbKWOc9Ez/TAwyWxNXeoV9c1v6FIeYiBieIWkpLjauysF18NzgR1MBNBXf8/KABdlkX68nAhlwcDFLGPCQ=="
|
|
36
|
crossorigin=""
|
|
37
|
></script>
|
|
38
|
<title>React App</title>
|
|
39
|
</head>
|
|
40
|
<body>
|
|
41
|
<noscript>You need to enable JavaScript to run this app.</noscript>
|
|
42
|
<div id="root"></div>
|
|
43
|
<!--
|
|
44
|
This HTML file is a template.
|
|
45
|
If you open it directly in the browser, you will see an empty page.
|
|
46
|
|
|
47
|
You can add webfonts, meta tags, or analytics to this file.
|
|
48
|
The build step will place the bundled scripts into the <body> tag.
|
|
49
|
|
|
50
|
To begin the development, run `npm start` or `yarn start`.
|
|
51
|
To create a production bundle, use `npm run build` or `yarn build`.
|
|
52
|
--></body>
|
|
53
|
</html>
|
