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

@booru/vite-plugin-moleculer-runner

v0.0.7

Published

- This is created as a quick solution for problems I encountered during setting up `esm typescript moleculer project`. This was a quick and dirty solution which I later refined a bit as a node module.

Downloads

380

Readme

Vite Plugin for moleculer-esm-runner

Why

  • This is created as a quick solution for problems I encountered during setting up esm typescript moleculer project. This was a quick and dirty solution which I later refined a bit as a node module.

What is this ?

  • This is a plugin to easily run moleculer applications using moleculer-runner.
    • for further information check https://github.com/moleculerjs/moleculer repository
  • This wraps around moleculer esm runner and use ViteDevServer HMR to easily reload the services.

Usage

  • create vanilla vite project using npx create-vite@latest, Choose Vanilla + Typescript
  • install runner as dev dependency
    • npm i -D @booru/vite-plugin-moleculer-runner
    • you may also need to install following to fully setup moleculer app
      • dependencies
        • moleculer
        • moleculer-repl
      • devDependencies
        • glob
        • dotenv
        • ts-node
  • add vite.config.ts file with below content
import {defineConfig} from 'vite'
import {resolve} from 'path'
import {MoleculerRunner} from '@booru/vite-plugin-moleculer-runner'
import glob from 'glob'

export default defineConfig({
    plugins: [
        MoleculerRunner.init({})
    ],
    build: {
        ssr: true,
        target: 'ESNext',
        lib: {
            entry: [
                ...glob.sync("**/*.service.ts", { absolute: false, cwd: '.' }).map(o=>resolve(__dirname, o)),
                resolve(__dirname, 'moleculer.config.ts')
            ]
        },
        rollupOptions:{
            output:[
                {
                    dir: 'dist',
                    format: 'es',
                    preserveModules: false,
                    entryFileNames: '[name].mjs',
                }
            ]

        },
        copyPublicDir: false
    },
    resolve: {alias: {"src": resolve('src/')}},

})

  • if required update tsconfig.json if required
{
  "compilerOptions": {
    "target": "ESNext",
    "useDefineForClassFields": true,
    "module": "ESNext",
    "lib": ["ESNext"],
    "skipLibCheck": true,

    "moduleResolution": "Node",
    "allowImportingTsExtensions": true,
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,

    "esModuleInterop": true,
    "strict": true,
    "noUnusedLocals": false,
    "noUnusedParameters": false,
    "noFallthroughCasesInSwitch": true
  },
  "include": [
    "**.ts"
  ],
  "ts-node": {
    "esm": true,
    "experimentalSpecifierResolution": "node"
  },
  "exclude": ["node_modules"]
}
  • Now you can run application in dev mode using npm run dev