Comparing version 0.1.0 to 0.1.1
{ | ||
"name": "moo", | ||
"version": "0.1.0", | ||
"version": "0.1.1", | ||
"description": "Optimised tokenizer/lexer generator! 🐄 Uses /y for performance. Moo!", | ||
@@ -5,0 +5,0 @@ "main": "moo.js", |
@@ -35,3 +35,3 @@ ![](cow.png) | ||
First, you need to do the needful: ~~`$ npm install moo`, `$ yarn install moo`, or whatever will ship this code to your computer~~ _Hold up a second; we haven't published to NPM yet!_ Alternatively, grab the `moo.js` file by itself and slap it into your web page via a `<script>` tag; it's completely standalone. | ||
First, you need to do the needful: `$ npm install moo`, `$ yarn install moo`, or whatever will ship this code to your computer. Alternatively, grab the `moo.js` file by itself and slap it into your web page via a `<script>` tag; it's completely standalone. | ||
@@ -38,0 +38,0 @@ Then you can start roasting your very own lexer/tokenizer: |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
0
21799