Merge pull request #38 from HenrikJoreteg/modernize

Modernize

Author: HenrikJoreteg

.circleci/config.yml

@@ -1 +1,2 @@
 node_modules
+dist

.gitignore

@@ -1,34 +1,34 @@
 # html-parse-stringify
 
-This is an *experimental lightweight approach* to enable quickly parsing HTML into an AST and stringify'ing it back to the original string.
+This is an _experimental lightweight approach_ to enable quickly parsing HTML into an AST and stringify'ing it back to the original string.
 
-As it turns out, if you can make a the simplifying assumptions about HTML that all tags must be closed or self-closing. Which is OK for *this* particular application. You can write a super light/fast parser in JS with regex.
+As it turns out, if you can make a the simplifying assumptions about HTML that all tags must be closed or self-closing. Which is OK for _this_ particular application. You can write a super light/fast parser in JS with regex.
 
 "Why on earth would you do this?! Haven't you read: http://stackoverflow.com/questions/1732348/regex-match-open-tags-except-xhtml-self-contained-tags ?!?!"
 
 Why yes, yes I have :)
 
-But the truth is. If you *could* do this in a whopping grand total of ~600 bytes (min+gzip) as this repo shows. It potentially enables DOM diffing based on a HTML strings to be super light and fast in a browser. What is that you say? DOM-diffing?
+But the truth is. If you _could_ do this in a whopping grand total of ~600 bytes (min+gzip) as this repo shows. It potentially enables DOM diffing based on a HTML strings to be super light and fast in a browser. What is that you say? DOM-diffing?
 
-Yes. 
+Yes.
 
-React.js essentially pioneered the approach. With React you render to a "virtual DOM" whenever you want to, and the virtual DOM can then diff against the real DOM (or the last virtual DOM) and then turn that diff into whatever transformations are necessary to get the *real* DOM to match what you rendered as efficiently as possible.
+React.js essentially pioneered the approach. With React you render to a "virtual DOM" whenever you want to, and the virtual DOM can then diff against the real DOM (or the last virtual DOM) and then turn that diff into whatever transformations are necessary to get the _real_ DOM to match what you rendered as efficiently as possible.
 
 As a result, when you're building a single page app, you don't have to worry so much about bindings. Instead, you simple re-render to the virtual DOM whenever you know something's changed. All of a sudden being able to have `change` events for individual properties becomes less important, instead you can just reference those values in your template whenever you think something changed.
 
 Cool idea, right?!
 
-## So why this? 
+## So why this?
 
-Well, there are other things React expects me to do if I use it that I don't like. Such as the custom templating and syntax you have to use. 
+Well, there are other things React expects me to do if I use it that I don't like. Such as the custom templating and syntax you have to use.
 
-If, hypothetically, you could instead diff an HTML string (generated by *whatever* templating language of your choice) against the DOM, then you'd get the same benefit, sans React's impositions. 
+If, hypothetically, you could instead diff an HTML string (generated by _whatever_ templating language of your choice) against the DOM, then you'd get the same benefit, sans React's impositions.
 
 This may all turn out to be a bad idea altogether, but initial results seem promising when paired with [virtual-dom](https://github.com/Matt-Esch/virtual-dom).
 
 But you can't just diff HTML strings, as simple strings, very easily, in order to diff two HTML node trees you have to first turn that string into a tree structure of some sort. Typically, the thing you generate from parsing something like this is called an AST (abstract syntax tree).
 
-This lib does exactly that. 
+This lib does exactly that.
 
 It has two methods:
 
@@ -51,13 +51,12 @@ See comments in the following example:
 var HTML = require('html-parse-stringify')
 
 // this html:
-var html = '<div class="oh"><p>hi</p></div>';
+var html = '<div class="oh"><p>hi</p></div>'
 
 // becomes this AST:
-var ast = HTML.parse(html);
+var ast = HTML.parse(html)
 
-
-console.log(ast);
+console.log(ast)
 /*
 {
     // can be `tag`, `text` or `component`
@@ -134,10 +133,14 @@ properties:
 - `voidElement` - `true` or `false`. Whether this tag is a known void element as defined by [spec](http://www.w3.org/html/wg/drafts/html/master/syntax.html#void-elements).
 - `children` - it will still have a `children` array, but it will always be empty.
 
+## changelog
+
+- `2.0.0` updated to more modern dependencies/build system. Switched to prettier, etc. No big feature differences, just new build system/project structure.
+- `1.0.0 - 1.0.3` no big changes, bug fixes and speed improvements.
 
 ## credits
 
-If this sounds interesting you should probably follow [@HenrikJoreteg](https://twitter.com/henrikjoreteg) and [@Philip_Roberts](https://twitter.com/philip_roberts) on twitter to see how this all turns out. 
+If this sounds interesting you should probably follow [@HenrikJoreteg](https://twitter.com/henrikjoreteg) and [@Philip_Roberts](https://twitter.com/philip_roberts) on twitter to see how this all turns out.
 
 ## license
 

.jshintignore

@@ -1,27 +1,27 @@
-declare var htmlParseStringify: htmlParseStringify.htmlParseStringify;
+declare var htmlParseStringify: htmlParseStringify.htmlParseStringify
 
 declare module htmlParseStringify {
-    export interface htmlParseStringify {
-        new (): htmlParseStringify;
-        parse_tag(tag: string): IDoc;
-        parse(html: string, options: IOptions): Array<any>;
-        stringify(doc: IDoc): string;
-    }
+  export interface htmlParseStringify {
+    new (): htmlParseStringify
+    parse_tag(tag: string): IDoc
+    parse(html: string, options: IOptions): Array<any>
+    stringify(doc: IDoc): string
+  }
 
-    export interface IDoc {
-        type: string;
-        content?: string;
-        voidElement: boolean;
-        name: string;
-        attrs: {};
-        children: IDoc[];
-    }
+  export interface IDoc {
+    type: string
+    content?: string
+    voidElement: boolean
+    name: string
+    attrs: {}
+    children: IDoc[]
+  }
 
-    export interface IOptions {
-        components: string[];
-    }
+  export interface IOptions {
+    components: string[]
+  }
 }
 
-declare module "html-parse-stringify" {
-    export = htmlParseStringify;
+declare module 'html-parse-stringify' {
+  export = htmlParseStringify
 }