npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@lu.se/vue-template

v4.0.0

Published

Components for LU template

Readme

Vue components for LU web template

This is the source for the node module @lu.se/vue-template. For an example using this module see johandalabacka/vue-template-test.

Example page

NOTE (October 2025): This package was rewritten to use Vue's (and vue-i18n's use of) Composition API in version 3.2.0. If you need to use the legacy approach with the Options API you need use <=v3.1.5.

Example

App.vue (from vue-template-test)

<template>
  <LuHeader
    :navbarmenu="menu"
    :topmenu="menu"
    :mobilemenu="menu"
    has-login
    has-search
    empty-search
    :is-logged-in="isLoggedIn"
    avatar="JD"
    logo-url="https://www.lth.se"
    :logo-src="`${baseUrl}lumall/images/logo/lth_logo_${locale}.svg`"
    :logo-title="t('lth_full')"
    compact
    @login="login"
    @logout="logout"
  />

  <!-- key is hack to redraw component then locale changes -->
  <LuBreadCrumb
    v-if="true"
    :key="locale"
  />

  <LuMain
    :leftmenu="menu"
    compact
    last-updated="2021-11-30"
    :page-manager-mail="t('page_manager')"
    :page-manager-notice="t('mail_only_for_support')"
  >
    <router-view />
  </LuMain>
  <LuToTop />
  <LuFooter
    :contact="{ name: t('lth_full'), box: '118', zip: '221 00', phone: '046-222 72 00', mail: '[email protected]' }"
    :logo-src="`${baseUrl}lumall/images/logo/lth_logo_footer_${locale}.svg`"
    :logo-title="t('lth_full')"
    :short-cuts="menu"
  />
</template>

<script setup>
import { computed, ref } from 'vue'
import { useI18n } from 'vue-i18n'
import { LuHeader, LuBreadCrumb, LuMain, LuFooter, LuToTop } from '@lu.se/vue-template/index.js'

import menuData from './menu.js'

const baseUrl = import.meta.env.BASE_URL
const isLoggedIn = ref(false)

const login = function() {
  isLoggedIn.value = true
}

const logout = function() {
  isLoggedIn.value = false
}

const menu = computed(() => menuData)
const { t, locale } = useI18n()
</script>

Setup

This package defines a Vue plugin that "auto-installs" the icons and internationalisation (i18n) strings the package itself needs. You can use that plugin and just define the i18n messages and icons you need for your app. Alternatively you can manually import what is needed. See below for the two approaches.

i18n

All components use vue-i18n for internationalization. The package's internationalization (i18n) strings need to be merged into your application's vue-i18n instance.

Details: In order to not pollute your app's set of i18n strings more than necessary, all string keys from this package are prefixed with luvt (for Lund University Vue template). E.g. the full slug for the header's login string is: luvt.header.login.

To merge this package's i18n strings and your application's (as well as provide the icons), there are two ways:

  1. Automatically merge through the Vue plugin defined by this package.
  2. Do the merging manually yourself.

Approach #1: Vue plugin

For this approach you basically only need to add two lines:

import luTemplate from '@lu.se/vue-template'
// ...
app.use(luTemplate, i18n)

From main.js (from vue-template-test), a demo app to show how to use this package:

<script setup>
import { createApp } from 'vue'
import App from './App.vue'
// ...
import { createI18n } from 'vue-i18n'
// Import the self-installing plugin from the LU Vue Template package:
import luTemplate from '@lu.se/vue-template'

// ...

// Your own translations
import en from './locales/en.json'
import sv from './locales/sv.json'

const messages = {
  sv,
  en,
}

const i18n = createI18n({
  locale: useLocalStorage('language', 'sv').value,
  fallbackLocale: 'sv',
  legacy: false,
  allowComposition: true,
  mode: 'composition',
  messages,
  // ...
})

const app = createApp(App)
app.use(i18n)
// This Vue plugin self-installs all i18n messages and icons the package needs.
app.use(luTemplate, i18n) // note: needs to come after `app.use(i18n)` line
// ...
</script>

Approach #2: manual merging

If you want to have more control the package exports a messages object containing all translation strings used by the components. You can then merge these messages with your application's i18n configuration like below.

  • N.B. that in this case you also need to import the icons for the package as well, included in the following code.

Using main.js (from vue-template-test) again as an example:

<script setup>
import { createApp } from 'vue'
import App from './App.vue'
// ...
import { createI18n } from 'vue-i18n'
import { messages as lumallMessages } from '@lu.se/vue-template'

// The icons:
import { library } from '@fortawesome/fontawesome-svg-core'
import { FontAwesomeIcon } from '@fortawesome/vue-fontawesome'
import { faChevronCircleUp } from '@fortawesome/pro-solid-svg-icons'
import {
  faBars,
  faChevronDoubleDown,
  faChevronDoubleUp,
  faChevronDown,
  faChevronRight,
  faCircleNotch,
  faGlobe,
  faMinusCircle,
  faPlusCircle,
  faSearch,
  faSignIn,
  faSignOut,
  faTimes,
} from '@fortawesome/pro-light-svg-icons'

// ...

// Your own translations
import localeEn from './locales/en.json'
import localeSv from './locales/sv.json'

// Merge this package's i18n strings with your own:
const messages = {
  sv: {
    ...lumallMessages.sv,
    ...localeSv, 
  },
  en: {
    ...lumallMessages.en,
    ...localeEn,
  },
}

const i18n = createI18n({
  locale: useLocalStorage('language', 'sv').value,
  fallbackLocale: 'sv',
  legacy: false,
  allowComposition: true,
  mode: 'composition',
  messages,
  // ...
})

// Also add the icons to the library:
library.add(
  faBars,
  faChevronCircleUp,
  faChevronDoubleDown,
  faChevronDoubleUp,
  faChevronDown,
  faChevronRight,
  faCircleNotch,
  faGlobe,
  faMinusCircle,
  faPlusCircle,
  faSearch,
  faSignIn,
  faSignOut,
  faTimes,
)

const app = createApp(App)
app.use(i18n)
// note: no need to use the `app.use` statement from approach #1 here
app.component('FaIcon', FontAwesomeIcon)
// however, you need to include the above line (for the icons)
// ...
</script>

I18n translation Keys

There exists translations for Swedish (sv) and English (en). The locale specification format used in this package is ISO 639.

Recap from above: in order to not pollute your app's set of i18n strings more than necessary, all string keys from this package are prefixed with luvt (for Lund University Vue template). [..]

The translation keys are thus generally in this format:

luvt.<component>.<slug>

E.g. for the LuHeader component:

Header Component

  • luvt.header.menu - Menu button label
  • luvt.header.search - Search button/field label
  • luvt.header.showHideSearch - Accessibility label for search toggle
  • ...

ToTop Component

Some components only have one string and are thus only named with the slug:

  • luvt.to_top - Back to top button label

Components

LuHeader, LuBreadCrumb, LuMain, LuFooter is to be at top level in your app. The other components are used by them and you don't need to import them.

LuHeader

This is the header of the page containing logo, search field, language switcher. Optional menus one on the top and one below logo and search field. Language switcher sets the key language in local storage to sv or en.

props

Name | Description | Default value ----|-----------|------------- topmenu | menu on top of the page. If not set, the menu will not show | undefined navbarmenu | menu below header. If not set, the menu will not show| undefined mobilemenu | menu shown on mobile narrow pages | false hasLogin | A login/logout button is added | false isLoggedIn | Is user logged in (show login or logout) | false avatar | show first two letters of string instead of logout icon | '' hasSearch | A search field is added | false emptySearch | Search field is emptied after search | false searchPlaceholder | Placeholder for search field | '' logoSrc | URL for the image | '' logoTitle | title and alt text | '' logoUrl | URL then clicking the logo | '' compact | Less padding on height | false

events

Name|Payload|Description ----|-----------|------------- @login | -- | User has clicked log in @logout | -- | User has clicked log out @search | "search string" | User has made a search

LuBreadCrumb

Uses router to create a breadcrump of current and all parent pages. This component is optional. It uses no props and takes all information from the router.

LuMain

props

Name | Description | Default value ----|-----------|------------- leftmenu | Menu to the left. If not set will the menu not show and content will use the whole width. | null lastUpdated | Date of last update | '' pageManagerMail | Mail address of page manager | '' pageManagerNotice | Notice under the page manager / date | '' compact | Less padding on top | false

slots

Name | Description ----|----------- default | content of page

LuRow

A row with space for an optional right column. Is used inside LuMain. You can have several rows stacked on each other.

slots

Name | Description ----|----------- default | central content right-column | content to the right. Goes below default content on smaller screens.

LuFooter

props

Name | Description | Default value ----|-----------|------------- contact | Object with the following properties name, box (number), zip, phone and mail | null logoSrc | URL for the image | '' logoTitle | title and alt text | '' shortCuts | menu of shortcuts. Always contains t('luvt.footer.shortcuts'). | null

LuInfobox

A box which is usually inside the right-column slot of a LuRow.

props

Name | Description | Default value ----|-----------|------------- title | The title of the box, required prop | undefined

slots

Name | Description ----|----------- default | content of the box

LuSpinner

A loading/waiting spinner.

props

Name | Description | Default value ----|-----------|------------- text | text to show | t('luvt.spinner.loading')

LuToTop

A button which is shown if page is scrolled a bit down (pageYOffset > 500). No props or events.

Menu example

path are vue-router paths and url are ordinary a href:s.

export default [{
  id: 'start',
  label: 'start',
  path: '/',
},
{
  id: 'lu',
  label: 'lu',
  url: 'http://www.lu.se',
},
{
  id: 'admin',
  label: 'admin',
  children: [
    {
      id: 'page1',
      label: 'page1',
      path: '/page1',
    },
  ],
},
{
  id: 'page2',
  label: 'page2',
  path: '/page2',
  children: [{
    id: 'page3',
    label: 'page3',
    path: '/page2/page3',
  },
  {
    id: 'page4',
    label: 'page4',
    path: '/page2/page4',
  },
  {
    id: 'google',
    label: 'google',
    url: 'https://www.google.com',
  }],
}]

All items in menu should have a unique id, a label and a path (internal page) or url (external page). In the router definition, if meta.title for a route is defined that is used as the title of page instead of the route's name.

How-to install

To use it in a project, e.g. with npm:

npm add '@lu.se/vue-template'

Install lu-template

Get a hold of the LU webmall (unfortunately not publically available anymore), unpack it and rename the folder to lumall and put it in the public folder.

Provide key for the FontAwesome Pro icons

Please refer to their documentation here and here.

index.html

<!DOCTYPE html>
<html lang="sv">

<head>
  <meta charset="utf-8">
  <meta http-equiv="x-ua-compatible" content="ie=edge">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Article Page: Default | Lunds universitet</title>
  <link media="all" rel="stylesheet" href="./lumall/styles/main.css">
  <link rel="apple-touch-icon" sizes="180x180" href="./lumall/apple-touch-icon.png">
  <link rel="icon" type="image/png" sizes="32x32" href="/lumall/favicon-32x32.png">
  <link rel="icon" type="image/png" sizes="16x16" href="/lumall/favicon-16x16.png">
  <link rel="manifest" href="./lumall/site.webmanifest">
  <link rel="mask-icon" href="./lumall/safari-pinned-tab.svg" color="#875e29">
  <meta name="msapplication-TileColor" content="#875e29">
  <meta name="theme-color" content="#875e29">
</head>

<body>
  <div id="app"></div>
  <script type="module" src="/src/main.js"></script>
</body>

</html>

Then refer to the Setup section above.