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 🙏

© 2024 – Pkg Stats / Ryan Hefner

ec-frontend-library

v3.0.9

Published

[![CircleCI](https://circleci.com/gh/illuminateeducation/ec-frontend-library/tree/develop.svg?style=shield&circle-token=22b92ce38a0379eba4bb1d8a6c6a31a0d12b860b)](https://circleci.com/gh/illuminateeducation/ec-frontend-library/tree/develop)

Downloads

1

Readme

ec-frontend-library

CircleCI

Consuming project setup

npm install -D babel-plugin-transform-imports
npm install @illuminateeducation/ec-frontend-library

ec-frontend-library

application setup

main.js

import Vue from 'vue'
import App from './App.vue'
import { Defaults, EcUpdateTheme, EcFrontendLibrary, EcFrontendVuetify, GetVuetifyInstance } from '@illuminateeducation/ec-frontend-library'
import '@illuminateeducation/ec-frontend-library/dist/ec-frontend-library.css'

Vue.use(EcFrontendLibrary, {
    axios: {
        withCredentials: true,
        baseURL: process.env.VUE_APP_BASE_URI ? process.env.VUE_APP_BASE_URI.replace(/localhost/g, location.host) : ''
    },
    authx: 'auth-x.host.com',
})

Vue.use(EcFrontendVuetify)

let vuetify = GetVuetifyInstance({
    options: {
        customProperties: true
    },
    iconfont: 'fa',
    theme: {
        dark: false,
        themes: Defaults.ecThemes
    }
})

EcUpdateTheme(Defaults.ecThemes.light) // creates CSS variable equivalents of all variables for use in local components
                                       // with something like the following: var(--fe-primary);
Vue.config.productionTip = false
Vue.prototype.$vuetify = vuetify
new Vue({
    vuetify,
    render: h => h(App),
}).$mount('#app')


Axios and Auth-x are optional

.npmrc

@illuminateeducation:registry=https://registry.npmjs.org/
//registry.npmjs.org/:_authToken=${NPM_TOKEN}

.babel.config.js

module.exports = {
  presets: [
    '@vue/app'
  ],
  "plugins": [
    [
      "transform-imports",
      {
        "vuetify": {
          "transform": "vuetify/es5/components/${member}", // eslint-disable-line no-template-curly-in-string
          "preventFullImport": true
        }
      }
    ]
  ]
}

To add CSS to entire project, add class ec-fe-lib to <body>. To add CSS only to imported CL components, add class ec-fe-lib to <div> surrounding the imported component.


ec-frontend-library setup and modification

npm install

Build dist

npm run build

Run your tests

npm run test

Lints and fixes files

npm run lint

Publishing to npm

Only if authorized to do so

  1. Make sure branch builds npm run build and review the dist directory
  2. Update version in package.json and package-lock.json
  3. Commit and push your branch
  4. Create a PR, have it reviewed and merged
  5. tag and release https://help.github.com/en/articles/creating-releases.

make sure to follow semantic versioning 0.1.0 (breaking).(feature).(patch or bugs) actual names if using npm version ... is major.minor.patch