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

sweetjs-compiler

v1.0.2

Published

Compiler for sweet.js macro

Downloads

6

Readme

sweetjs-compiler

Compiler for sweet.js macro

Summary

The sweetjs-compiler is a simple wrapper to the exist compile method in the sweet.js module. It is usefull when you want compile your macro but it is not necessarily inside a file.

Use

Sweetjs-compiler is a npm module therefore is enought to make:

npm install --save sweetjs-compiler

And in the your code:

const SweetCompiler = require('sweetjs-compiler')

Options

The constructur require an object with the follow params:

SweetCompiler({
  ambient: { type: String, default: process.cwd() },
  noBabel: { type: Boolean, default: false },
  resolver: { type: Function, default: node_module_resolver },
  loader: { type: Function, default: node_module_loader }
});

ambient

Directory where start the search of the require macro. Any import in the souce code is relative at the path set here.

noBabel

Set if using Babel for the back-end or not.

resolver

The function to get the path of the macro included in the source.

loader

The function to read the content of the macro included in the source.

Compile

The only method of sweetjs-compiler is compile. It take in input the source and return an object with:

  • code - The expended code
  • sourceMap - The source map

If some errors is occurred, an exception is throw.

Example:

const SweetCompiler = require('sweetjs-compiler');

var compiler = new SweetCompiler({
  // So, everywhere you run the script, the path to include 
  // the macro in the source files is fixed
  ambient: __dirname 
});

// The example in the home of sweet.js
var source = "syntax hi = function (ctx) {return #`console.log('hello, world!')`;} hi";

try {
  var out = compiler.compile(source);
  console.log(out.code) // Print: console.log('hello, world!')
  
} catch (err) {
  /*
  ...
  */
}

Note

This project is make to use the method compile in a javascript program. Please, if this is a unneccessary solution, open a issue so I will delete this garbage.