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

@divmain/babel-generator

v6.6.0-0

Published

Turns an AST into code.

Downloads

4

Readme

babel-generator

Turns an AST into code.

Install

$ npm install babel-generator

Usage

import {parse} from 'babylon';
import generate from 'babel-generator';

const code = 'class Example {}';
const ast = parse(code);

const output = generate(ast, { /* options */ }, code);

Options

Options for formatting output:

name | type | default | description -----------------------|----------|-----------------|-------------------------------------------------------------------------- auxiliaryCommentBefore | string | | Optional string to add as a block comment at the start of the output file auxiliaryCommentAfter | string | | Optional string to add as a block comment at the end of the output file shouldPrintComment | function | opts.comments | Function that takes a comment (as a string) and returns true if the comment should be included in the output. By default, comments are included if opts.comments is true or if opts.minifed is false and the comment contains @preserve or @license retainLines | boolean | false | Attempt to use the same line numbers in the output code as in the source code (helps preserve stack traces) comments | boolean | true | Should comments be included in output compact | boolean or 'auto' | opts.minified | Set to true to avoid adding whitespace for formatting minified | boolean | false | Should the output be minified concise | boolean | false | Set to true to reduce whitespace (but not as much as opts.compact) quotes | 'single' or 'double' | autodetect based on ast.tokens | The type of quote to use in the output filename | string | | Used in warning messages

Options for source maps:

name | type | default | description -----------------------|----------|-----------------|-------------------------------------------------------------------------- sourceMaps | boolean | false | Enable generating source maps sourceMapTarget | string | | The filename of the generated code that the source map will be associated with sourceRoot | string | | A root for all relative URLs in the source map sourceFileName | string | | The filename for the source code (i.e. the code in the code argument). This will only be used if code is a string.

AST from Multiple Sources

In most cases, Babel does a 1:1 transformation of input-file to output-file. However, you may be dealing with AST constructed from multiple sources - JS files, templates, etc. If this is the case, and you want the sourcemaps to reflect the correct sources, you'll need to make some changes to your code.

First, each node with a loc property (which indicates that node's original placement in the source document) must also include a loc.filename property, set to the source filename.

Second, you should pass an object to generate as the code parameter. Keys should be the source filenames, and values should be the source content.

Here's an example of what that might look like:

import {parse} from 'babylon';
import traverse from "babel-traverse";
import generate from 'babel-generator';

const a = 'var a = 1;';
const b = 'var b = 2;';
const astA = parse(a, { filename: 'a.js' });
const astB = parse(b, { filename: 'b.js' });
const ast = {
  type: 'Program',
  body: [].concat(astA.body, ast2.body)
};

const { code, map } = generate(ast, { /* options */ }, {
  'a.js': a,
  'b.js': b
});

// Sourcemap will point to both a.js and b.js where appropriate.