jan
/
mustache.js
spegling av https://github.com/janl/mustache.js
Bevaka 1
Stjärnmärk 0
Förgrening 0
Kod Ärenden 0 Släpp 46 Wiki Aktiviteter
Du kan inte välja fler än 25 ämnen Ämnen måste starta med en bokstav eller siffra, kan innehålla bindestreck ('-') och vara max 35 tecken långa.
789 Incheckningar
19 Grenar
8.1MB
Träd: 1de94bbdd3
Grenar Taggar
${ item.name }
Skapa branchen ${ searchTerm }
från '1de94bbdd3'
${ noResults }
mustache.js/package.json

package.json 1.9KB
Rå Normal View Historik

Parser rewrite This commit is a complete rewrite of the core mustache.js file with two main goals: 1) a major performance boost and 2) better compliance with the mustache spec. In order to improve performance templates are pre-compiled to JavaScript functions. These compiled functions take a view, a partials object, and an optional callback as arguments. They are cached to prevent unnecessary re-compilation of an already compiled template. Both of these enhancements facilitate a generous boost in performance. A few other notes: - The mustache.js file is now both browser and CommonJS ready without any modification. - The API exposes two main methods: Mustache.compile and Mustache.render. The former is used to generate a function for a given template, while the latter is a higher-level function that is used to compile and render a template in one shot. Mustache.to_html is still available for backwards compatibility. - The concept of pragmas is removed to conform more closely to the original mustache spec. The dot symbol still works to reference the current item in an array. - The parser is much more strict about whitespace than it was before. The rule is simple: if a line contains only a non-variable tag (i.e. not {{tag}} or {{{tag}}}) and whitespace, that line is ignored in the output. Users may use the "space" option when compiling templates to preserve every whitespace character in the original template. - The parser is able to provide detailed information about where errors occur when parsing and rendering templates, including the line number and surrounding code context.
14 år sedan
​
:ship: bump to version 4.0.1
6 år sedan
Parser rewrite This commit is a complete rewrite of the core mustache.js file with two main goals: 1) a major performance boost and 2) better compliance with the mustache spec. In order to improve performance templates are pre-compiled to JavaScript functions. These compiled functions take a view, a partials object, and an optional callback as arguments. They are cached to prevent unnecessary re-compilation of an already compiled template. Both of these enhancements facilitate a generous boost in performance. A few other notes: - The mustache.js file is now both browser and CommonJS ready without any modification. - The API exposes two main methods: Mustache.compile and Mustache.render. The former is used to generate a function for a given template, while the latter is a higher-level function that is used to compile and render a template in one shot. Mustache.to_html is still available for backwards compatibility. - The concept of pragmas is removed to conform more closely to the original mustache spec. The dot symbol still works to reference the current item in an array. - The parser is much more strict about whitespace than it was before. The rule is simple: if a line contains only a non-variable tag (i.e. not {{tag}} or {{{tag}}}) and whitespace, that line is ignored in the output. Users may use the "space" option when compiling templates to preserve every whitespace character in the original template. - The parser is able to provide detailed information about where errors occur when parsing and rendering templates, including the line number and surrounding code context.
14 år sedan
​
add homepage property to package.json
11 år sedan
Fixing npm warnings
13 år sedan
​
​
​
changed mocha reporter to spec and bumped mocha version, solves #403
11 år sedan
​
​
​
​
​
added .js to main property in package.json
13 år sedan
Created command line tool. CLI used to render a mustache template with a data view, writes the template into stdout when successfull. Otherwise meaningfull errors into stderr. Fixes #424
11 år sedan
​
​
Specifying files in package.json Good npm citizens should specify which files a npm module consists of so module users dont have to download all the unnecessary things.
11 år sedan
​
Introduce build step to generate `.js | .min.js` from `.mjs` By making the main source code an ES module placed in `mustache.mjs`, what used to be in `mustache.js` is now built based off of the ES module source inside `mustache.mjs`. This is done primarily to avoid breaking existing projects already using mustache.js, by keeping the UMD-version in `mustache.js` part of the git repository in addition to the minified version in `mustache.min.js`. After experiment with several compilers; - Babel - TypeScript - Rollup and examining their build output, [Rollup](https://rollupjs.org/) was chosen because of the UMD output it creates which closely resembles what we've historically had in the previous `mustache.js` source code. The contents of `.js | .min.js` files has been generated by running the following npm script: ``` $ npm run build ``` Also change linting w/eslint to target the `.mjs` file, since the output of rollup that ends up in the old `mustache.js` file is not sensible to do linting on.
6 år sedan
Specifying files in package.json Good npm citizens should specify which files a npm module consists of so module users dont have to download all the unnecessary things.
11 år sedan
​
​
​
​
Add volo support Fixes #249
13 år sedan
Fixes AMD registration, volo package.json entry This change allows the AMD define signature to match what common AMD optimizers use to find define calls that need naming. Also updates the volo package.json entry so that the correct version of mustache can be fetched properly.
12 år sedan
Run tests using node on Travis
14 år sedan
Run jshint before tests. - Documented required version of npm while developing - Use the latest npm client for node >= v0.8 on travis Special quirks to get node v0.6 supported: - npm client v1.3.26 on travis - jshint 2.4.4 as >= 2.5.x breaks
11 år sedan
​
​
Run tests using node on Travis
14 år sedan
Introduce build step to generate `.js | .min.js` from `.mjs` By making the main source code an ES module placed in `mustache.mjs`, what used to be in `mustache.js` is now built based off of the ES module source inside `mustache.mjs`. This is done primarily to avoid breaking existing projects already using mustache.js, by keeping the UMD-version in `mustache.js` part of the git repository in addition to the minified version in `mustache.min.js`. After experiment with several compilers; - Babel - TypeScript - Rollup and examining their build output, [Rollup](https://rollupjs.org/) was chosen because of the UMD output it creates which closely resembles what we've historically had in the previous `mustache.js` source code. The contents of `.js | .min.js` files has been generated by running the following npm script: ``` $ npm run build ``` Also change linting w/eslint to target the `.mjs` file, since the output of rollup that ends up in the old `mustache.js` file is not sensible to do linting on.
6 år sedan
Separate tests run on legacy Node.js versions Primarily because it's getting to be a pain in the backside to always consider pre Node.js 6 when wanting to use up-to-date dependencies.
6 år sedan
Introduce build step to generate `.js | .min.js` from `.mjs` By making the main source code an ES module placed in `mustache.mjs`, what used to be in `mustache.js` is now built based off of the ES module source inside `mustache.mjs`. This is done primarily to avoid breaking existing projects already using mustache.js, by keeping the UMD-version in `mustache.js` part of the git repository in addition to the minified version in `mustache.min.js`. After experiment with several compilers; - Babel - TypeScript - Rollup and examining their build output, [Rollup](https://rollupjs.org/) was chosen because of the UMD output it creates which closely resembles what we've historically had in the previous `mustache.js` source code. The contents of `.js | .min.js` files has been generated by running the following npm script: ``` $ npm run build ``` Also change linting w/eslint to target the `.mjs` file, since the output of rollup that ends up in the old `mustache.js` file is not sensible to do linting on.
6 år sedan
Separate tests run on legacy Node.js versions Primarily because it's getting to be a pain in the backside to always consider pre Node.js 6 when wanting to use up-to-date dependencies.
6 år sedan
Added browser tests. Covers the project with browser tests, not only V8 via node/iojs. Tests are runned with [zuul](https://github.com/defunctzombie/zuul) which provides simple local browser testing, aswell as cloud testing on multiple browsers with [saucelabs](http://saucelabs.com).
11 år sedan
​
​
​
changed mocha reporter to spec and bumped mocha version, solves #403
11 år sedan
​
Unpin chai and eslint versions greenkeeper.io will let us know if the minor/patch bumps break our code, so go wild.
10 år sedan
Bump eslint v2 -> v6 Primarily because it's been ages since we bumped eslint and as a precursor to allowing some future test files to be written in a more modern type of JavaScript. Especially think about tests written using puppeteer.js which is heavily `Promise` based, where the async-await syntax makes it soooo less painful to write. Silly not being able to use that because of an outdated eslint version doesn't understand that syntax construct at all.
6 år sedan
Install release tools with npm rather than via pre-commit hook (#666) Previously mocha, uglifyjs and jshint used when publishing a new version were ensured / installed by `Rakefile` via the pre-commit git hook. Those modules were automatically installed globally if not present in `$PATH`. Installing modules globally has one particular downside that we should avoid: we can't ensure developers publishing new mustache.js versions have the same version of these 3rd party modules installed. If instead we make these modules local dev dependencies, we can ensure which versions are installed, and we make 3rd party dependencies explicit by listing them in `package.json`, rather than in `Rakefile`.
7 år sedan
chore(package): update mocha to version 3.0.2 (#588) https://greenkeeper.io/
9 år sedan
Add CI test verifying Mustache works in browser's global scope This is a precursor to introducing a build step that will change what we expose from this package. Better off writing some tests to verify existing projects with different module systems continue to work as expected.
6 år sedan
Introduce build step to generate `.js | .min.js` from `.mjs` By making the main source code an ES module placed in `mustache.mjs`, what used to be in `mustache.js` is now built based off of the ES module source inside `mustache.mjs`. This is done primarily to avoid breaking existing projects already using mustache.js, by keeping the UMD-version in `mustache.js` part of the git repository in addition to the minified version in `mustache.min.js`. After experiment with several compilers; - Babel - TypeScript - Rollup and examining their build output, [Rollup](https://rollupjs.org/) was chosen because of the UMD output it creates which closely resembles what we've historically had in the previous `mustache.js` source code. The contents of `.js | .min.js` files has been generated by running the following npm script: ``` $ npm run build ``` Also change linting w/eslint to target the `.mjs` file, since the output of rollup that ends up in the old `mustache.js` file is not sensible to do linting on.
6 år sedan
Install release tools with npm rather than via pre-commit hook (#666) Previously mocha, uglifyjs and jshint used when publishing a new version were ensured / installed by `Rakefile` via the pre-commit git hook. Those modules were automatically installed globally if not present in `$PATH`. Installing modules globally has one particular downside that we should avoid: we can't ensure developers publishing new mustache.js versions have the same version of these 3rd party modules installed. If instead we make these modules local dev dependencies, we can ensure which versions are installed, and we make 3rd party dependencies explicit by listing them in `package.json`, rather than in `Rakefile`.
7 år sedan
Use ngrok rather than localtunnel when running browser tests (#668) These changes makes zuul use ngrok for exposing itself to the outside world, rather than the default localtunnel implementation. That's because we've had quite a lot of issues with flakyness which seems to be related to localtunnel, e.g.: ``` - starting: <internet explorer 9 on Windows 2008> events.js:160 throw er; // Unhandled 'error' event ^ Error: connection refused: localtunnel.me:44896 (check your firewall settings) at Socket.<anonymous> (/home/travis/build/janl/mustache.js/node_modules/localtunnel/client.js:84:32) at emitOne (events.js:96:13) at Socket.emit (events.js:188:7) at emitErrorNT (net.js:1290:8) at _combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickCallback (internal/process/next_tick.js:104:9) ``` I thought this was fixed by [using Node.js 6 instead of Node.js 4](https://github.com/janl/mustache.js/pull/667), but sadly that was not the case as it re-appeared with Node.js 6 as well. Had to use a [custom version of zuul-ngrok](https://github.com/rase-/zuul-ngrok/pull/12) which contains a newer version of ngrok. The dependency used by the upstream module threw an error when running on my computer, the updated version worked as a charm though. We should change to using the upstream module as soon as the PR with that ngrok version bump lands. Set `concurrency: 1` otherwise ngrok would fail and make IE11 tests stall forever because of too many connections being made within a short time period. I've notice it can take quite some time (20+ minutes) to get all the tests through as it seems ngrok still seems to throttle the connections somehow, but the important thing is getting these tests to work.
7 år sedan
​
Add spm support
11 år sedan
Second shot at having greenkeeper ignore eslint (#610) First shot at getting greenkeeper to ignoring eslint updates landed with commit 85fa74325845771fb3a5229ba319aa15bb57f3c3. Sadly that commit had a minor `greenkeper` misspelling in package.json, which obviously didn't have much effect for greenkeeper. This commit fixes that blooper in hopes that greenkeeper will stop opening PRs about new eslint versions, as we don't want to update at the moment cause eslint 3.x requires Node.js v4.x.
9 år sedan
:ship: bump to version 2.3.0
9 år sedan
​
​
Ignore eslint for greenkeeper updates. (#580) As we don't plan to update to Node.js v4 any time soon, we can't update eslint cause it requires Node.js => v4.
9 år sedan
Add license attribute https://docs.npmjs.com/files/package.json#license http://npm1k.org/
11 år sedan
Parser rewrite This commit is a complete rewrite of the core mustache.js file with two main goals: 1) a major performance boost and 2) better compliance with the mustache spec. In order to improve performance templates are pre-compiled to JavaScript functions. These compiled functions take a view, a partials object, and an optional callback as arguments. They are cached to prevent unnecessary re-compilation of an already compiled template. Both of these enhancements facilitate a generous boost in performance. A few other notes: - The mustache.js file is now both browser and CommonJS ready without any modification. - The API exposes two main methods: Mustache.compile and Mustache.render. The former is used to generate a function for a given template, while the latter is a higher-level function that is used to compile and render a template in one shot. Mustache.to_html is still available for backwards compatibility. - The concept of pragmas is removed to conform more closely to the original mustache spec. The dot symbol still works to reference the current item in an array. - The parser is much more strict about whitespace than it was before. The rule is simple: if a line contains only a non-variable tag (i.e. not {{tag}} or {{{tag}}}) and whitespace, that line is ignored in the output. Users may use the "space" option when compiling templates to preserve every whitespace character in the original template. - The parser is able to provide detailed information about where errors occur when parsing and rendering templates, including the line number and surrounding code context.
14 år sedan
 1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162 
  1. {

  2.   "name": "mustache",

  3.   "version": "4.0.1",

  4.   "description": "Logic-less {{mustache}} templates with JavaScript",

  5.   "author": "mustache.js Authors <http://github.com/janl/mustache.js>",

  6.   "homepage": "https://github.com/janl/mustache.js",

  7.   "repository": {

  8.     "type": "git",

  9.     "url": "https://github.com/janl/mustache.js.git"

  10.   },

  11.   "keywords": [

  12.     "mustache",

  13.     "template",

  14.     "templates",

  15.     "ejs"

  16.   ],

  17.   "main": "./mustache.js",

  18.   "bin": {

  19.     "mustache": "./bin/mustache"

  20.   },

  21.   "files": [

  22.     "mustache.js",

  23.     "mustache.mjs",

  24.     "mustache.min.js",

  25.     "bin",

  26.     "wrappers",

  27.     "LICENSE"

  28.   ],

  29.   "volo": {

  30.     "url": "https://raw.github.com/janl/mustache.js/{version}/mustache.js"

  31.   },

  32.   "engines": {

  33.     "npm": ">=1.4.0"

  34.   },

  35.   "scripts": {

  36.     "build": "rollup mustache.mjs --file mustache.js --format umd --name Mustache --banner '// This file has been generated from mustache.mjs' && uglifyjs mustache.js > mustache.min.js",

  37.     "test": "npm run test-lint && npm run test-unit",

  38.     "test-lint": "eslint mustache.mjs bin/mustache test/**/*.js",

  39.     "test-unit": "mocha --reporter spec test/*-test.js",

  40.     "test-render": "mocha  --reporter spec test/render-test",

  41.     "pre-test-browser": "node test/create-browser-suite.js",

  42.     "test-browser": "npm run pre-test-browser && zuul -- test/context-test.js test/parse-test.js test/scanner-test.js test/render-test-browser.js",

  43.     "test-browser-local": "npm run pre-test-browser && zuul --local 8080 -- test/context-test.js test/scanner-test.js test/parse-test.js test/render-test-browser.js"

  44.   },

  45.   "devDependencies": {

  46.     "chai": "^3.4.0",

  47.     "eslint": "^6.5.1",

  48.     "jshint": "^2.9.5",

  49.     "mocha": "^3.0.2",

  50.     "puppeteer": "^2.0.0",

  51.     "rollup": "^1.26.3",

  52.     "uglify-js": "^3.4.6",

  53.     "zuul": "^3.11.0",

  54.     "zuul-ngrok": "nolanlawson/zuul-ngrok#patch-1"

  55.   },

  56.   "greenkeeper": {

  57.     "ignore": [

  58.       "eslint"

  59.     ]

  60.   },

  61.   "license": "MIT"

  62. }