@author Nabil Redmann repo@bananaacid.de, @license MIT
... all natively in the browser.
- uses VUE 3 (unmodified, vanilla)
- .vue files support (using https://github.com/FranckFreiburger/vue3-sfc-loader)
- no server logic (static)
- no compile, no vite/webpack ...
- no node_modules
- ESM module based code
- native JS import maps
- script-module
- LESS and PUG support
Basic additions:
- VueUse
Optional Test additions:
- Vuetify
... and typescript just works out of the box (thanks vue? or chrome browser?)
Note:
-
Pug support might not work within stackblitz at times in /v1. Outside of Stackblitz: always.
-
initially long loading times might happen within stackblitz, due to the /v1 folder having a complete project within.
-
moving the module code into a main.js would feel even more like a vite project.
The npm package name is vue3-esm-browser-vueengine.
First add the basic dependencies:
<script type="importmap" id="vueBasics">
{
"imports": {
"vue": "https://unpkg.com/vue@3/dist/vue.esm-browser.prod.js",
"vue-router": "https://unpkg.com/vue-router@4/dist/vue-router.esm-browser.prod.js",
"vue3-sfc-loader": "https://unpkg.com/vue3-sfc-loader@0.9.5/dist/vue3-sfc-loader.esm.js",
"less": "https://cdn.jsdelivr.net/npm/less@4/dist/less.min.js/+esm"
}
}
</script>To include the main script at the end of your html, either download it, or add it remotely with <script type="module" id="vueEngine" src="https://unpkg.com/vue3-esm-browser-vueengine"></script>
Folder structure (static server!)
./components (optional)
./pages (optional)
./views (optinoal)
app.vue
index.html
The usual .vue file setup.
You need to setup your HTML:
- add
<style>xmp {display: none; }</style>to the<head> - body needs an element with id app, like
<body> <div id="app">loading ...</app> - below that:
- configure
vueConfig.routesin a<script type="module" async>block (see below) - include below the 2 script elements:
#vueBasics#vueEngine(see Installation)
- configure
Now just edit your app.vue and add pages (views) and components. For each page added, adjust your vueConfig.routes.
Note: to use local not CDN
In the #vueBasics importmap, you can change the paths to local versions. The PugJS dependency path can be changed by setting globalThis.vueConfig.mappings.pugjs='./libs/pug.js'
You can deactivate the import for LessCSS and PugJS: If you remove the import for less from the inputmap and set the pugjs=null.
Only App.vue, all in one, in index.html -> /example-minimal
- do the
Basic setupabove- the 3.1. is not required: do not configure the
vueConfig.routes, you do not need the async block.
- the 3.1. is not required: do not configure the
- either add a
App.vueblock (seeSimple setup) or an./App.vuein the same folder as the index.html
All in ONE, in index.html
- do the
Basic setupabove - add components and pages to your index.html, after 3.1. (your configuration) and definitely before the 3.2. (the Vue basics)
- at least, add a
app.vuecomponent
- at least, add a
in order not to load from external .vue files, you can embed pages and components within your index.html. (If they are not embedded, the engine will try to load them from the server.)
-
idis the filename for internal use, or in case you manually want to import it. Components will be globally initialized with the BaseName.-
<xmp type="component" id="vueuseTest/MousePos.vue">=> use<MousePos />-- orimport MousePos from '/components/vueuseTest/MousePos.vue';
-
-
typecan be-
="page"or="component"or="view"- the internal path for page will become/pages/Home.vueand for the component/components/MyComponent.vueand for view/views/TopArea.vue -
="app"- will not be prefixed with a folder (but with a slash:/SomeThing.vue) - mind the plural: folders are ending in
s - You can always use subpaths in the id (but the filenames MUST BE UNIQUE)
-
supported:
<script setup> and <script lang="ts"> (both can be mixed),
<template lang="pug"> and <style lang="less">
<xmp type="page" id="Home.vue">
<template>
</template>
<script setup>
</script>
<style scoped>
</style>
</xmp>Why <xmp>?
It is next to <textarea> the only tag, that allows any tag within and does NOT change the tag-name to all lower case (which would break <MyComponent /> and would only allow <kebab-case />).
The App is mounted with the <App /> tag as basic template. You need to provide an App.vue
Example:
<xmp type="app" id="App.vue">
<template>
<RouterView />
</template>
</xmp>additionally to the above, you can:
- configure
vueConfig.routes - configure
vueConfig.componentsandvueConfig.imports - add an importmap
#vueImportsUserDefined - hook into
vueConfig.onReady - watch
loadingStatesfor loading progress
Any of this is optional.
globalThis.vueConfig.routes = [
{ path: '/', page: 'Home.vue', component: undefined },
// ...
]Helps configuring the vue-router plugin.
- path: the path to bind to
-
page: the filename of the
/pages/*page to automatically load and initialize as component - component: if you load and initialize the component yourself instead of the page (component has precedence over the page property), manual instantiating see: https://stackoverflow.com/a/76136400/1644202
Noteworthy:
-
name: a shorthand for
<RouterLink to="name">to use -
meta: additional
vue-routersupported configuration
... and any other config option vue-router supports.
globalThis.vueConfig.components = [
{ name: 'TestMe', file: '/components/TestMe.vue' },
];load components to be globally available they do not need to be imported in a vue file. (If not added to this array, you need to import them as you normally would.)
Embedded components (in index.html) are loaded automatically to be globally available without adding them here.
- name is the component name for Vue to use
- file is the local path or remote URL to load it from
globalThis.vueConfig.imports = [
{ type: string, content: string|function|Promise },
...
]For scripts that add to window (window == globalThis). Will be added after options is defined.
- content => url
To load a plugin: like using import() with app.use() or for handling stuff that had been loaded with type: 'script'. Will be called after createApp().
- content => async fn({app, options, vue}) {...}
To add styles or stylesheet urls. Use @import url("...") to load a file. Will be added after options is defined.
- content => css string
<script type="importmap" id="vueImportsUserDefined">
{
"imports": {
"@vueuse/shared": "https://cdn.jsdelivr.net/npm/@vueuse/shared@13/index.min.mjs",
"@vueuse/core": "https://cdn.jsdelivr.net/npm/@vueuse/core@13/index.min.mjs"
}
}
</script>An importmap script block MUST BE PURE JSON !
The import names (keys), are what you can use in your import statements, as you usually would in NodeJS, Deno, Bun, ... this ist the browser version. (import { useMouse } from '@vueuse/core';)
The import urls can be a local path or a remote URL.
The id is optional.
Note: Imports must be propper ES6 Modules ! They must use export.
globalThis.vueConfig.onReady = (mountCallback) => {
console.log('Vue app is ready and will be mounted');
mountCallback();
};
This gives you the opportunity to handle a preload screen or alike, then trigger the app mounting.
If onReady is not set, the Vue app will be mounted automatically when everything is prepared.
Accessing globalThis.loadingStates, you get the current loading stage. As of writing, there are 11.
You could watch for changes in that array for progress on loading. vueConfig.onReady gives you a reliable trigger when it is done.
Example:
<div id="app">
<progress max="11"></progress> <br /> <div id="status"></div>
</div>globalThis.loadingStates = new Proxy([], {
set: (target, prop, changes) => {
target[prop] = changes;
// handle status update
const el = document.querySelector('#status');
if (prop !== 'length' && el) el.innerHTML += '<br>' + changes;
if (prop == 'length' && el)
document.querySelector('progress').value = changes;
return true;
},
});
// set first status (before the engine pushes the others)
globalThis.loadingStates.push( 'Preparing and loading dependencies' );Only commonjs imports are a problem.
@vueuse/shared must be in an importmap, but @vueuse/core must be in options.moduleCache to work.
Side note: script[type=importmap] tags do nothing when added by javascript.
So what is there to do? The importmap for custom modules has to be created by the user, but all keys from importmaps will be added to options.moduleCache automatically.
The technical parts are all done allready.
These are optional things I want to include, to have a single drop in solution.
- [E] (ERROR) add a styles folder and test importing in style-less-tags (with .css and .less), and .css imports in script-tags
- [x] test: can routesConfig moved to a script-module-tag and add to globalThis just by exporting? How could the main script access the config?
- [x] importsConfig (index.html), to make imports easier
- [x] move main module code to ./lib/vueEngine.mjs
- [x] make sure, everything is consolidated into the mjs. To be imported and handle everything like an engine (like we used to with jquery and angular and vue).