jan
/
mustache.js
ミラー元 https://github.com/janl/mustache.js
ウォッチ 1
スター 0
フォーク 0
コード 課題 0 リリース 46 Wiki アクティビティ
選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。
831 コミット
19 ブランチ
8.1MB
ツリー: 4ae8c8a9df
ブランチ タグ
${ item.name }
ブランチ ${ searchTerm } を作成
'4ae8c8a9df' から
${ noResults }
mustache.js/package.json

package.json 2.1KB
Raw 通常表示 履歴

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年前
​
4.2.0
5年前
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年前
​
add homepage property to package.json
11年前
Fixing npm warnings
13年前
​
​
​
changed mocha reporter to spec and bumped mocha version, solves #403
11年前
​
​
​
​
​
Update and simplify package.json
6年前
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年前
​
​
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年前
Update and simplify package.json
6年前
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年前
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年前
Update and simplify package.json
6年前
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年前
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
5年前
​
​
​
​
​
​
Add volo support Fixes #249
13年前
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年前
Run tests using node on Travis
14年前
​
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
5年前
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年前
Include linting of `test/*.js` in `npm run test-lint` script Had obviously been forgotten, but those test files should have been part of the ordinary lint phase. The fact that we had forgotten to lint these files, allowed a missing semi-colon to sneak into `./test/cli-test.js` file. Refs https://github.com/janl/mustache.js/pull/777
5年前
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.
5年前
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年前
​
​
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.
5年前
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.
5年前
​
changed mocha reporter to spec and bumped mocha version, solves #403
11年前
​
upgrade npm modules to more recent versions which don't break the tests
1年前
​
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
5年前
upgrade npm modules to more recent versions which don't break the tests
1年前
​
​
​
​
​
​
​
​
​
​
​
Add spm support
11年前
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年前
:ship: bump to version 2.3.0
9年前
​
​
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年前
Add license attribute https://docs.npmjs.com/files/package.json#license http://npm1k.org/
11年前
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年前
 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172 
  1. {

  2.   "name": "mustache",

  3.   "version": "4.2.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 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": "^4.4.1",

  51.     "eslint": "^8.57.0",

  52.     "esm": "^3.2.25",

  53.     "jshint": "^2.13.6",

  54.     "mocha": "^10.4.0",

  55.     "puppeteer": "^10.4.0",

  56.     "rollup": "^4.17.2",

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

  58.     "zuul": "^3.12.0",

  59.     "zuul-ngrok": "^4.0.0"

  60.   },

  61.   "overrides": {

  62.     "zuul-ngrok": {

  63.       "ngrok": "^4.3.3"

  64.     }

  65.   },

  66.   "greenkeeper": {

  67.     "ignore": [

  68.       "eslint"

  69.     ]

  70.   },

  71.   "license": "MIT"

  72. }