jan
/
mustache.js
miroir de https://github.com/janl/mustache.js
Suivre 1
Ajouter aux favoris 0
Bifurcation 0
Code Tickets 0 Versions 46 Wiki Activité
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
821 Révisions
19 Branches
8.1MB
Aborescence: ea3adcfc93
Branches Tags
${ item.name }
Créer la branche ${ searchTerm }
de 'ea3adcfc93'
${ noResults }
mustache.js/package.json

package.json 2.0KB
Brut Vue normale Historique

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.
il y a 14 ans
​
:ship: bump to version 4.1.0
il y a 5 ans
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.
il y a 14 ans
​
add homepage property to package.json
il y a 11 ans
Fixing npm warnings
il y a 13 ans
​
​
​
changed mocha reporter to spec and bumped mocha version, solves #403
il y a 11 ans
​
​
​
​
​
Update and simplify package.json
il y a 6 ans
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
il y a 11 ans
​
​
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.
il y a 11 ans
Update and simplify package.json
il y a 6 ans
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.
il y a 6 ans
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.
il y a 11 ans
Update and simplify package.json
il y a 6 ans
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.
il y a 11 ans
Add package.json `exports` field (#773) These changes adds an `exports` field to package.json with the main goal of allowing the root/main export to be our ESM syntax version of the package, as opposed to the UMD/CommonJS version. This will make it easier for using projects written with ESM to use mustache.js out of the box, without having to figure out that they'd have to `import mustache/mustache.mjs` to get the ESM version. It is also assumed to be beneficial for tools like http://skypack.dev to choose the correct ESM version when appropriate. Refs https://nodejs.org/api/packages.html#packages_package_entry_points
il y a 5 ans
​
​
​
​
​
​
Add volo support Fixes #249
il y a 13 ans
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.
il y a 12 ans
Run tests using node on Travis
il y a 14 ans
​
Rename .mjs -> .js to make it ESM and not have build output in git Although we'll now end up with only `mustache.js` in the git repo, being written in ESM syntax, the npm package will still be as before: - `mustache.js`: UMD, meaning CommonJS, AMD or global scope - `mustache.mjs`: ESM
il y a 5 ans
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.
il y a 6 ans
Rename .mjs -> .js to make it ESM and not have build output in git Although we'll now end up with only `mustache.js` in the git repo, being written in ESM syntax, the npm package will still be as before: - `mustache.js`: UMD, meaning CommonJS, AMD or global scope - `mustache.mjs`: ESM
il y a 5 ans
Avoid use of `esm` when running tests on legacy Node.js versions Because `esm` does not support legacy versions of Node.js, at least not below Node.js 6 as of writing this, we have to avoid using that whenever tests are running on legacy versions. But now that the source code (`mustache.js`) is written in ESM syntax, how on earth are we going to run tests on these legacy versions of Node.js? We gotta run the build step first, so that we end up with a `mustache.js` file in CJS, or strictly speaking it will be UMD. That's kinda pain in the backside isn't it? Yes, but running tests on legacy versions are not meant to be done locally, but rather in CI. That means we can easily automate the flow of (1) building the source code before (2) starting the test suite. For our futureselves, if we want to stop running tests on legacy versions of Node.js; the changes introduces in this commit, could be removed completely.
il y a 5 ans
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).
il y a 11 ans
​
​
Bump `mustache.js` version via npm script instead of git pre-commit hook Primarily because installing `git` hooks are easy to forget for maintainers, whilst telling `npm` to do something as a consequence of `$ npm version <patch | minor | major>` is seamless. Also worth mentioning we what we used to do in the pre-commit hook script is now greatly simplified as we don't want to have the build output and/or the `.min.js` in git anymore. Therefore, as long as we've bumped the version number in the source code, we're basically done, after having amended that change into the git commit the `npm` CLI creates.
il y a 5 ans
Build ESM -> CJS before running legacy Node.js tests and packaging tests Because the source code is written in ESM syntax and we cannot use the `esm` package to make `require()` ESM compatible, since that package does not support legacy versions of Node.js. Also in our usage tests in CI, we need to mimck the npm packaging behaviour where building is involved.
il y a 5 ans
​
changed mocha reporter to spec and bumped mocha version, solves #403
il y a 11 ans
​
Unpin chai and eslint versions greenkeeper.io will let us know if the minor/patch bumps break our code, so go wild.
il y a 10 ans
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.
il y a 6 ans
Use `esm` package locally when testing to use ESM syntax from CJS code These changes are primarily aiming for having an acceptable developer experience when working on changes locally and want to run the test suite. By using `esm` as a required package to be executed *before* the individual test files are executed, `esm` allows CommonJS/`require()` based code to use code written with ES Modules syntax. In practise that means our existing CommonJS based test suite that is `require()`ing the source code witten in ES Modules, is seamless and totally transparent. It just works without any build or transpiling pipeline like `babel` involved. Caveat: the `esm` package only support Node.js 6.x and above. That is more than okey, as we've got continous integration to verify how our changes works on different versions of Node.js, browsers & deno. Refs https://www.npmjs.com/package/esm
il y a 5 ans
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`.
il y a 7 ans
chore(package): update mocha to version 3.0.2 (#588) https://greenkeeper.io/
il y a 9 ans
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.
il y a 6 ans
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.
il y a 6 ans
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`.
il y a 7 ans
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.
il y a 7 ans
​
Add spm support
il y a 11 ans
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.
il y a 9 ans
:ship: bump to version 2.3.0
il y a 9 ans
​
​
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.
il y a 9 ans
Add license attribute https://docs.npmjs.com/files/package.json#license http://npm1k.org/
il y a 11 ans
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.
il y a 14 ans
 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667 
  1. {

  2.   "name": "mustache",

  3.   "version": "4.1.0",

  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.     "bin/",

  23.     "mustache.mjs",

  24.     "mustache.min.js",

  25.     "wrappers/"

  26.   ],

  27.   "exports": {

  28.     ".": {

  29.       "import": "./mustache.mjs",

  30.       "require": "./mustache.js"

  31.     },

  32.     "./*": "./*"

  33.   },

  34.   "volo": {

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

  36.   },

  37.   "scripts": {

  38.     "build": "cp mustache.js mustache.mjs && rollup mustache.mjs --file mustache.js --format umd --name Mustache && uglifyjs mustache.js > mustache.min.js",

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

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

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

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

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

  44.     "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",

  45.     "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",

  46.     "postversion": "scripts/bump-version-in-source",

  47.     "prepublishOnly": "npm run build"

  48.   },

  49.   "devDependencies": {

  50.     "chai": "^3.4.0",

  51.     "eslint": "^6.5.1",

  52.     "esm": "^3.2.25",

  53.     "jshint": "^2.9.5",

  54.     "mocha": "^3.0.2",

  55.     "puppeteer": "^2.0.0",

  56.     "rollup": "^1.26.3",

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

  58.     "zuul": "^3.11.0",

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

  60.   },

  61.   "greenkeeper": {

  62.     "ignore": [

  63.       "eslint"

  64.     ]

  65.   },

  66.   "license": "MIT"

  67. }