Skip to content

A tokenizer that looks like a stream for JavaScript and node.js

Notifications You must be signed in to change notification settings

Floby/node-tokenizer

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

64 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Build Status

Synopsis

A wide purpose tokenizer for JavaScript. The interface follows more or less the WriteStream from node.js.

node-tokenizer is published on npm so you can install it with npm install tokenizer

How to

  • require the Tokenizer constructor
var Tokenizer = require('tokenizer');
  • construct one (we'll see what the callback is used for)
var t = new Tokenizer(mycallback);
  • add rules
t.addRule(/^my regex$/, 'type');
  • write or pump to it
t.write(data);
// or
stream.pipe(t);
  • listen for new tokens
t.on('token', function(token, type) {
    // do something useful
    // type is the type of the token (specified with addRule)
    // token is the actual matching string
})
// alternatively you can use the tokenizer as a readable stream.
  • look out for the end
t.on('end', callback);

the optional callback argument for the constructor is a function that will be called for each token in order to specify a different type by returning a string. The parameters passed to the function are token(the token that we found) and match, an object like this

{
    regex: /whatever/ // the regex that matched the token
    type: 'type' // the type of the token
}

Have a look in the example folder

Rules

rules are regular expressions associated with a type name. The tokenizer tries to find the longest string matching one or more rules. When several rules match the same string, priority is given to the rule which was added first. (this may change)

Please note that your regular expressions should use ^ and $ in order to test the whole string. If these are not used, you rule will match every string that contains what you specified, this could be the whole file!

To do

  • a lot of optimisation
  • being able to share rules across several tokenizers (although this can be achieved through inheritance)
  • probably more hooks
  • more checking

License

MIT

Copyright (c) 2012 Florent Jaby

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

About

A tokenizer that looks like a stream for JavaScript and node.js

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •