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

rakudo

v0.43.0

Published

Install node 10.16.0 or 12.11.1 from https://nodejs.org

Downloads

67

Readme

Dependencies

Install node 10.16.0 or 12.11.1 from https://nodejs.org

Getting started with node.js rakudo.js

The easiest way is to install the rakudo package from npm

mkdir tutorial-project # Create a fresh project directory
cd tutorial-project
npm init
npm install --save rakudo
./node_modules/.bin/perl6-js -e 'say "Hello World"'

Using a node.js module

cd tutorial-project
npm install --save chalk

To use node.js modules you need to specify where they should be looked for. use lib 'nodejs#/your/path/to/node/modules' is a good way to do that

use lib 'nodejs#' ~ $*PROGRAM.parent.add('node_modules').absolute;
use chalk:from<node.js>;
say("Hello {chalk.blue("Blue")} World");

Keep in mind that if you load a node.js module during precompilation it gets reloaded at runtime, so it's internal state gets lost.

Interoperability with JS

Passing :lang to eval will execute the passed code as JavaScript.

my $document = EVAL(:lang, 'return document')

You can access attributes of those objects using postcircumfix:<{ }> (you should often use the <> shorcut) You can call methods on the the objects using regular Perl 6 syntax.

$document<body>.appendChild($document.createTextNode('Hello World'));

Primitive JS data types are converted rather then wrapped

| JavaScript | Perl6 | | -------------|-------| | true | True | | false | False | | String | Str | | null | Mu | | undefined | Mu | | BigInt | Int | | Number | Num |

A Perl 6 Mu when passed to JS land ends up as null

To pass values to Perl 6 land the executed code needs a return.

EVAL(:lang<JavaScript>, '123') # This returns Mu
EVAL(:lang<JavaScript>, 'return 123') # This returns 123

Extra methods on wrapped JS objects

In order to enable using wrapped objects in Perl 6 land wrapped objects offer some methods that Perl 6 expects.

  • sink

    Does nothing.

  • defined

    Always returns True

  • Bool

    Always returns True

  • item

    Returns the object it is called on

  • new

    Uses the JavaScript new operator to create an new instance

    my $Date = EVAL(:lang<JavaScript>, 'return Date');
    my $instance = $Date.new('December 17, 1995 03:24:00');
    say($instance.getFullYear()); # 1995

If the wrapped object has method of that same name you can use an :INTERNAL modifier to access it.

$obj.new(:INTERNAL, 123) | -------------|-------|

This will call a js new method rather then doing ``new $obj(123)```