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

mamps

v0.1.6

Published

## Project setup ``` npm install ```

Downloads

10

Readme

mamps

Project setup

npm install

Compiles and hot-reloads for development

npm run serve

Compiles and minifies for production

npm run build

Run your unit tests

npm run test:unit

Run your end-to-end tests

npm run test:e2e
npm run test:e2e -- --headless

Recommended to run e2e tests in other pipeline not together with Build pipeline

Lints and fixes files

npm run lint

How to configure CI

1. Install npm packages (it could be configured through cache)
2. Run unit tests (with publishing test results)
3. Build app for specific stage (for example: npm run build -- --mode staging)
In the end there will be "/dist" folder in root directory, it should be copied in CD pipeline

How to configure fallback page for router

Link

Customize configuration

See Configuration Reference.

Install plugin

  1. Deploy the project locally
  2. n the file /mamps-frontend/src/vue-appolo.ts in the defaultOptions object, change the value of the field httpEndpoint : 'required backend address'
  3. in the file /mamps-frontend/package.json in the field name: 'set the required package name', in the field version: 'change the version to the last value +1' (example "version": "0.1.1" => "version" : "0.1.2",)
  4. after that you need to publish the package
  5. open the console in the root folder, then enter in npm login
  6. You will be asked to enter your login and password from the npm.com website.
  7. After that you need to publish the package npm publish
  8. If the publication was successful, you can follow the link and see the information about the package.
  9. After that you can install the package yourself.
  10. In file main.(js/ts) import component App from ~your-package-pame~/src/App.vue.
  11. Add component in your code ===
new Vue({  
    ...   
    render: h => h(App),  
}).$mount('#app')

===