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

streamparser

v1.1.0

Published

Simple parser, triggers events upon data receival and processing

Downloads

32

Readme

streamparser

Simple parser, triggers events upon data receival and processing.

Last updated at: 28-DEC-2015 21:15 GMT-2

Here we create any Readable Stream

var simpleparser = require('simpleparser');
var reader = new memstreams.ReadableStream();
//For comprehension sake we added this simple example w memory-streams.
reader.append('a;1-b;2-c;3-d;4');

Then we create a config object (this is optional - default is linebreak='\n' and no fieldbreak)

var config = {
         linebreak: '-',
         fieldbreak: ';'
     };`

Now we create the parser instance (remember config is optional)

    var p = new simpleparser(reader, config);
    //This will trigger every line read by the parser
    p.on('line', function (data) {
        expect(data.length).to.equal(2);
        if (data[0] === 'a') {
            expect(data[1]).to.equal('1')
        } else if (data[0] === 'b') {
            expect(data[1]).to.equal('2')
        } else if (data[0] === 'c') {
            expect(data[1]).to.equal('3')
        } else if (data[0] === 'd') {
            expect(data[1]).to.equal('4')
        }
    });

    //Once parsing has finished this is triggered
    p.on('end', function () {
        done();
    });

    //This is a key aspect. Parsing will not start unless this method is called
    p.resume();

});

Field Mapping

Now it is possible to define line templates and the parser will give you objects validated by regex and assembled on the event (as long as you inform it the templates in advance ;)).

See the sample below:

reader.append('a;1;2\nb;2;4\na;3;5');
var config = {
    linebreak: '\n',
    fieldbreak: ';',
    models: {
            a: {
                template: {F1: '\D*', F2: '\d*', F3: '\d*'},
                postprocess: function (obj) {
                    obj.F2 = obj.F2 + '--- TESTE - A'
                }
            },
            b: {
                template: {F1: '.*', F2: '.*', F3: '.*'},
                postprocess: function (obj) {
                    obj.F2 = obj.F2 + '--- TESTE - B;'
                }
            }
    }
};

Note that in this config we have set a property models, and inside it we have the model names (a,b). Base on the value found in the first field, the parser will match the template to be applied. Each model has the fields:

  • template: An object where each prop will reflect one field in the line (order is relevant). The value of each field is a STRING representing a REGEX that will be used to validate the value found by the parser. In case no validation is required, use the good ´n old '.*' regex to match anything. In case matching can not be achieved, parser will throw an error.
  • postprocess: This property is optional, and in case required, should point to a method that receives the assembled object as parameter and manipulates is after the whole line has been parsed. It allows you to change values of fields based on other fields, for example.

TODO:

~~1. Add objectmapper~~

~~2. Create multi doc mapping in the same stream~~

  1. You tell me :)