mweststrate / immer

100%

master: 99%

LAST BUILD ON BRANCH v2.1.1

branch: v2.1.1

CHANGE BRANCH

x

Reset

• v2.1.1
• 0.4.0
• 1.0.0
• aleclarson
• async-recipes
• ci
• ci/test-nodejs-6-8-10-11
• ci/use-yarn-cache
• code-cleanup
• curry
• curry2
• deep-freeze
• dependabot/npm_and_yarn/handlebars-4.5.1
• dependabot/npm_and_yarn/js-yaml-3.13.1
• dependabot/npm_and_yarn/lodash-4.17.13
• dependabot/npm_and_yarn/mixin-deep-1.3.2
• docs
• enable-codesandbox
• es5-dts
• factory
• feature/curry
• feature/fast-prune
• feature/reuse
• fix-362
• fix-map-instantiation
• fix/es5-array-delete-error
• frozen-return
• funding
• github-actions-ci
• hooks
• immer3
• immer3-v2
• improved-types
• isDraft
• issue-100
• issue-202
• issue-233
• issue-243
• issue-264
• issue-268
• issue-270
• issue-328
• issue-381
• jest24
• kachkaev-add-failing-tests-for-recursive-use
• map-fixes
• master
• new-immer-readme-image
• next
• nothing
• patch-1
• patch-2
• patch-fixes
• patch2
• patches
• perf3
• produce-with-patches
• promise
• pull/351/head
• seamless-immutable
• sucrase
• support_map_and_set
• symbols
• ts
• ts-3.4
• ts-3.4-inference-improvements
• ts-jest
• v0.3.0
• v0.4.2
• v0.5.0
• v0.6.0
• v0.8.2
• v1.1.0
• v1.1.1
• v1.1.2
• v1.1.3
• v1.10.0
• v1.10.1
• v1.10.2
• v1.10.3
• v1.10.4
• v1.10.5
• v1.11.0
• v1.11.1
• v1.12.0
• v1.12.1
• v1.2.0
• v1.4.0
• v1.5.0
• v1.7.0
• v1.7.1
• v1.7.3
• v1.7.4
• v1.8
• v1.8.0
• v1.8.0-alpha
• v1.8.1
• v1.8.2
• v1.9
• v1.9.0
• v1.9.1
• v1.9.2
• v1.9.3
• v2
• v2.0.0
• v2.0.0-alpha
• v2.1.0
• v2.1.2
• v2.1.3
• v2.1.4
• v2.1.5
• v2.2.0
• v3.0.0
• v3.1
• v3.1.0
• v3.1.1
• v3.1.2
• v3.1.3
• v3.1.4
• v3.2.0
• v3.2.1
• v3.3.0
• v4
• v4.0.0
• v4.0.1
• v4.0.2
• v5.0.0
• v5.0.1
• v5.0.2
• v5.1.0
• v5.2.0
• v5.2.1
• v5.3.0
• v5.3.1
• v5.3.2
• v5.3.3
• visited

Build # 788

Build Type

push

travis-ci

Committed by aleclarson

Commit Message

fix: share internal symbols between immer installations

The `nothing` symbol is still not portable across installations, since it never escapes any producer that returns it. The only reason this could be an issue is if an Immer-using library transparently wraps a user's function and asks them to install their own copy of Immer if they want to return `nothing` (in that case, the library should instead re-export `nothing` for its users).

Fixes #322

Run Details

348 of 350 branches covered (99.43%)

Branch coverage included in aggregate %.

399 of 399 relevant lines covered (100.0%)

539.21 hits per line