te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数 大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数 大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>javascript - node - how to use source-map with nyc and mocha - Stack Overflow

科技改变生活-雨落星辰 - 所有的伟大,都源于一个勇敢的开始

    最新消息：雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客
    你的位置： 首页>programmer>javascript - node - how to use source-map with nyc and mocha - Stack Overflow

    javascript - node - how to use source-map with nyc and mocha - Stack Overflow

    programmeradmin3浏览0评论

    So nyc is mangling my files as follows:

      at _onCreate (src/post/admin.js:1:10453)
  at doQuery (src/db.js:59:216)
  at process._tickCallback (internal/process/next_tick.js:68:7)

    I am unsure of how to use a source map to unmangle this. The docs state:

    Accurate stack traces using source-maps.

    When produce-source-map is set to true, then the instrumented source files will include inline source maps for the instrumenter transform. When bined with source-map-support, stack traces for instrumented code will reflect their original lines.

    So I tried the following npm run mand:

    "NODE_ENV=test nyc mocha --require ./tests/setup.js --require source-map-support/register --produce-source-map true --bail ./tests/unit/$FILE"

    bined with the nyc setting:

    "nyc": {
    "include": [
        "src"
    ],
    "exclude": [
        "./tmp/**/*",
        "./tests"
    ],
    "instrument": true,
    "report-dir": "./tests/coverage",
    "temp-dir": "./tests/temp",
    "source-map": true,
    "produce-source-map": true
}

    but the line is still mangled.

    So nyc is mangling my files as follows:

      at _onCreate (src/post/admin.js:1:10453)
  at doQuery (src/db.js:59:216)
  at process._tickCallback (internal/process/next_tick.js:68:7)

    I am unsure of how to use a source map to unmangle this. The docs state:

    Accurate stack traces using source-maps.

    When produce-source-map is set to true, then the instrumented source files will include inline source maps for the instrumenter transform. When bined with source-map-support, stack traces for instrumented code will reflect their original lines.

    So I tried the following npm run mand:

    "NODE_ENV=test nyc mocha --require ./tests/setup.js --require source-map-support/register --produce-source-map true --bail ./tests/unit/$FILE"

    bined with the nyc setting:

    "nyc": {
    "include": [
        "src"
    ],
    "exclude": [
        "./tmp/**/*",
        "./tests"
    ],
    "instrument": true,
    "report-dir": "./tests/coverage",
    "temp-dir": "./tests/temp",
    "source-map": true,
    "produce-source-map": true
}

    but the line is still mangled.

    • javascript
    • node.js
    • mocha.js
    • istanbul
    • nyc
    Share Improve this question asked Oct 24, 2018 at 1:39 A. LA. L 12.6k29 gold badges98 silver badges178 bronze badges
    Add a ment  | 

    1 Answer 1

    Reset to default 14 +50

    the basic pre-condition for it to work would be (as described here):

    npm install --save-dev source-map-support

    make sure nyc is ^10.3.2 (10.3.0 was broken).

    "devDependencies": {
    ...
    "mocha": "^3.3.0",
    "nyc": "^10.3.2",
    "source-map-support": "^0.4.15",
}

    the nyc config should be "sourceMap": true, "produce-source-map": true.

    and the documentation explains how to use them:

    CLI Usage

    node -r source-map-support/register piled.js

    Programmatic Usage

    Put the following line at the top of the piled file.

    require('source-map-support').install();

    one can also define mapping file-names by adding ments:

    //# sourceMappingURL=filename.js.map

    与本文相关的文章

    发布评论

    评论列表(0)

    1. 暂无评论