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 🙏

© 2026 – Pkg Stats / Ryan Hefner

quasar-easy-modules

v1.0.18

Published

With the help of this package, it is possible to easily set up the basic structure of the project and easily add new modules as well as add sub-modules to existing modules.

Readme

Quasar easy modules

With the help of this package, it is possible to easily set up the basic structure of the project and easily add new modules as well as add sub-modules to existing modules.

Setup

  • First you need to type node index.js in project terminal.

  • Now you are asked to select a module type. You have 3 choices:

    - Standalone Module

    - Composite Module

    - Add submodule to existing module

Standalone Module

If you selected Standalone Module you are now asked to enter module name. After giving a name of your choice, in the src -> modules new folder is created. If you for example gave a name auth, your folder structure will look like this:

  • auth
    • components (folder with .vue component and README.md file inside)
    • composables (folder with .ts file and README.md file inside)
    • middleware (folder with .ts file and README.md file inside)
    • pages (folder with .vue component and README.md file inside)
    • services (folder with .ts file and README.md file inside)
    • utils (folder with .ts file and README.md file inside)
    • README.md
    • routes.ts (here is created default route for the page component)
    • store.ts (here is created default example store)
    • types.ts (here is created default example interface)

You can modify every of this file.

Composite Module

If you selected Composite Module you are now asked to enter main module name. After giving a name of your choice, you are now asked to enter your submodule name. Now you are asked if you would like to define another submodule, and you can repeat that process. After you are finished in the src -> modules new folder is created. If you for example created main module named administration and submodules named auth and user your folder structure will look like this:

  • administration
    • auth
      • components (folder with .vue component and README.md file inside)
      • composables (folder with .ts file and README.md file inside)
      • middleware (folder with .ts file and README.md file inside)
      • pages (folder with .vue component and README.md file inside)
      • services (folder with .ts file and README.md file inside)
      • utils (folder with .ts file and README.md file inside)
      • README.md
      • routes.ts (here is created default route for the page component)
      • store.ts (here is created default example store)
      • types.ts (here is created default example interface)
    • user
      • components (folder with .vue component and README.md file inside)
      • composables (folder with .ts file and README.md file inside)
      • middleware (folder with .ts file and README.md file inside)
      • pages (folder with .vue component and README.md file inside)
      • services (folder with .ts file and README.md file inside)
      • utils (folder with .ts file and README.md file inside)
      • README.md
      • routes.ts (here is created default route for the page component)
      • store.ts (here is created default example store)
      • types.ts (here is created default example interface)
    • routes.ts (in this file will be places all the routes from submodules):
    export const adminRoutes: RouteRecordRaw[] = [
      ...authRoutes,
      ...userRoutes,];

Add submodule to existing module

If you selected Add submodule to existing module you are now asked to select main module in which you want to add submodule. You are now asked to enter your submodule name. Now you are asked if you would like to define another submodule, and you can repeat that process. If you for example selected main module named administration and entered submodules name company, in the src -> modules -> administration new folder named company.

Your folder structure will now look like this:

  • administration
    • auth
      • components (folder with .vue component and README.md file inside)
      • composables (folder with .ts file and README.md file inside)
      • middleware (folder with .ts file and README.md file inside)
      • pages (folder with .vue component and README.md file inside)
      • services (folder with .ts file and README.md file inside)
      • utils (folder with .ts file and README.md file inside)
      • README.md
      • routes.ts (here is created default route for the page component)
      • store.ts (here is created default example store)
      • types.ts (here is created default example interface)
    • user
      • components (folder with .vue component and README.md file inside)
      • composables (folder with .ts file and README.md file inside)
      • middleware (folder with .ts file and README.md file inside)
      • pages (folder with .vue component and README.md file inside)
      • services (folder with .ts file and README.md file inside)
      • utils (folder with .ts file and README.md file inside)
      • README.md
      • routes.ts (here is created default route for the page component)
      • store.ts (here is created default example store)
      • types.ts (here is created default example interface)
    • company
      • components (folder with .vue component and README.md file inside)
      • composables (folder with .ts file and README.md file inside)
      • middleware (folder with .ts file and README.md file inside)
      • pages (folder with .vue component and README.md file inside)
      • services (folder with .ts file and README.md file inside)
      • utils (folder with .ts file and README.md file inside)
      • README.md
      • routes.ts (here is created default route for the page component)
      • store.ts (here is created default example store)
      • types.ts (here is created default example interface)
    • routes.ts (in this file will be places all the routes from submodules)

*** Notice that your routes.ts has been updated, and now it contains routes for company submodule.

    export const adminRoutes: RouteRecordRaw[] = [
      ...authRoutes,
      ...userRoutes,
      ...companyRoutes,
  ];