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

@medusajs/admin

v7.1.17

Published

<p align="center"> <a href="https://www.medusajs.com"> <img alt="Medusa" src="https://user-images.githubusercontent.com/7554214/153162406-bf8fd16f-aa98-4604-b87b-e13ab4baf604.png" width="100" /> </a> </p> <h1 align="center"> @medusajs/admin </h1

Downloads

47,171

Readme

Getting started

Install the package:

yarn add @medusajs/admin

Add the plugin to your medusa-config.js:

module.exports = {
  // ...
  plugins: [
    {
      resolve: "@medusajs/admin",
      options: {
        // ...
      },
    },
  ],
  // ...
}

Configuration

The plugin can be configured with the following options:

| Option | Type | Description | Default | | ------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | serve | boolean? | Whether to serve the admin dashboard or not. | true | | path | string? | The path the admin server should run on. Should not be prefixed or suffixed with a slash. Cannot be one of the reserved paths: "admin" and "store". | "app" | | outDir | string? | Optional path for where to output the admin build files | undefined | | autoRebuild | boolean? | Decides whether the admin UI should be rebuild if any changes or a missing build is detected during server startup | false |

Hint: You can import the PluginOptions type for inline documentation for the different options:

module.exports = {
  // ...
  plugins: [
    {
      resolve: "@medusajs/admin",
      /** @type {import('@medusajs/admin').PluginOptions} */
      options: {
        path: "app",
      },
    },
  ],
  // ...
}

Building the admin dashboard

The admin will be built automatically the first time you start your server if you have enabled autoRebuild. Any subsequent changes to the plugin options will result in a rebuild of the admin dashboard.

You may need to manually trigger a rebuild sometimes, for example after you have upgraded to a newer version of @medusajs/admin, or if you have disabled autoRebuild. You can do so by adding the following script to your package.json:

{
  "scripts": {
    "build:admin": "medusa-admin build"
  }
}

Accessing the admin dashboard

The admin dashboard will be available at your-server-url/app, unless you have specified a custom path in the plugin options. If you are running your server locally on port 9000 with the default path "app", you will be able access the admin dashboard at http://localhost:9000/app.