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

laravel-queue

v1.1.10

Published

run job from laravel

Downloads

3

Readme

Codacy Badge Codacy Badge

node server for Laravel queue

NPM

Process job on laravel events

Getting started

Install and init module

Create package.json

npm init

Install laravel-queue

npm install --save laravel-queue

After init the application

./artisan init

It ask for laravel project path then ask for command path (relative to laravel project path) then when asked add this to Console/kernel.php

if your commands folder is not standard(e.g app/Console/Commands), dont forget to change namespace of the class

    \App\Console\Commands\NodeConfig::class

Import laravel config

./artisan laravel:config

It ask which config to import and show you setting to put to config in Config/laravel.js to automatically import with the same setting

If you need to interact with database (only tested with mysql) you can import model from database add model to import in Config/core.js and run

./artisan make:models

Example laravel event

<?php

namespace App\Events;

use App\Events\Event;
use Illuminate\Contracts\Broadcasting\ShouldBroadcastNow;
use Illuminate\Queue\SerializesModels;

class EventExample extends Event implements ShouldBroadcastNow
{
    use SerializesModels;
    //public variable send with event
    public $data;
    public $otherData;

    /**
     * Create a new event instance.
     *
     * @return void
     */
    public function __construct($dataToSend)
    {
        $this->data = $dataToSend;
        $this->otherData = 'otherData';
    }

    /**
     * Get the broadcast event name.
     * event name in javascript object notation
     * @return string
     *
     */
    public function broadcastAs()
    {
        return 'app.example';
    }

    /**
     * Get the channels the event should be broadcast on.
     *
     * @return array
     */
    public function broadcastOn()
    {
        return [config('broadcasting.channel', 'laravel-channel')];
    }
}

In Config/app.js add this in job

app: {
    example: "exampleJob"
}

then run this for create job

./artisan make:job

look at Jobs folder to test job, data is stored in job.data.

Complete documentation will come soon...

why use it

php artisan queue:listen use pooling and use cpu to check if job need to run

node is event-driven and do job when arrive so it use less cpu

to-do

  • [x] write test
  • [ ] write doc
  • [ ] import from other databases (postgresql,sqlite,...)

Stuff used to make this

Package

package forked and included