text:
chore(deps): update dev dependencies

This PR contains the following updates:

Package
Update
Type
Change
Sourcegraph

snapshot-diff
minor
devDependencies
0.4.0 -> 0.5.2

documentation
major
devDependencies
8.1.2 -> 12.1.2

rollup
major
devDependencies
0.66.2 -> 1.25.2

rollup-plugin-babel
major
devDependencies
3.0.7 -> 4.3.3

react-scripts
major
devDependencies
1.1.5 -> 3.2.0

Release Notes

thymikee/snapshot-diff
v0.5.1
Compare Source
Features

add stablePatchmarks option (#72, #74)

v0.5.0
Compare Source
Features:

add testName to toMatchDiffSnapshot (#64)
[BREAKING] bump jest@24, flow@0.91, babel@7 (#63)

v0.4.2
Compare Source
v0.4.1
Compare Source

documentationjs/documentation
v12.1.2
Compare Source
Bug Fixes

check for empty diff (#1273) (3e0958b)

v12.1.1
Compare Source
Bug Fixes

check for empty diff (#1273) (3e0958b)

v12.1.0
Compare Source
Features

Add git submodules support to github linking (#1270) (ec36b41)

12.0.3 (2019-07-22)
Bug Fixes

Allow skipped array arguments in destructuring. Fixes #1247 (#1266) (f9039e9)

12.0.2 (2019-07-16)
12.0.1 (2019-07-10)
Bug Fixes

Crash when called with no inputs. yargs now variadic positional arguments undefined instead of

v12.0.3
Compare Source
Features

Add git submodules support to github linking (#1270) (ec36b41)

12.0.3 (2019-07-22)
Bug Fixes

Allow skipped array arguments in destructuring. Fixes #1247 (#1266) (f9039e9)

12.0.2 (2019-07-16)
12.0.1 (2019-07-10)
Bug Fixes

Crash when called with no inputs. yargs now variadic positional arguments undefined instead of

v12.0.2
Compare Source
Bug Fixes

Allow skipped array arguments in destructuring. Fixes #1247 (#1266) (f9039e9)

v12.0.1
Compare Source
12.0.2 (2019-07-16)
v12.0.0
Compare Source

Formatted with Prettier (8f36e75)

BREAKING CHANGES

The next release will require Node 8

11.0.1 (2019-06-12)
Bug Fixes

toc with children getting displayed as "note" (#1253) (14298bb)

v11.0.1
Compare Source

Formatted with Prettier (8f36e75)

BREAKING CHANGES

The next release will require Node 8

11.0.1 (2019-06-12)
Bug Fixes

toc with children getting displayed as "note" (#1253) (14298bb)

v11.0.0
Compare Source
Bug Fixes

Fix parsing of optional parameters with annotations (ca17de5)

Features

Enable all parser plugins (fa1b0b5)
Support exportNamespaceFrom in parser (8fa141d)

BREAKING CHANGES

this removes support for legacy decorators, because
in one place we had legacy and in another we didn't.

v10.1.0
Compare Source
Bug Fixes

Fix parsing of optional parameters with annotations (ca17de5)

Features

Enable all parser plugins (fa1b0b5)
Support exportNamespaceFrom in parser (8fa141d)

BREAKING CHANGES

this removes support for legacy decorators, because
in one place we had legacy and in another we didn't.

v10.0.0
Compare Source
Features

TypeScript support & inference (3773e02)

v9.3.1
Compare Source
Features

Support custom babel config (#1205) (746d0a9)

BREAKING CHANGES

this may change babel configuration loading, and is a
major change to the documentation.js approach to Babel.

9.3.1 (2019-03-12)
v9.3.0
Compare Source
Features

Add inner section (#1212) (64c9ca6)

9.2.1 (2019-02-26)
v9.2.1
Compare Source
Features

Add inner section (#1212) (64c9ca6)

9.2.1 (2019-02-26)
v9.2.0
Compare Source
Bug Fixes

default theme: only render either note or section (fixes #1113) (#1206) (fb0a27f)

Features

Add favicon option (#1207) (5b045f2)

9.1.1 (2018-12-21)
Bug Fixes

inferred properties duplicating explicitly specified ones (2d0bd0e)

v9.1.1
Compare Source
Bug Fixes

default theme: only render either note or section (fixes #1113) (#1206) (fb0a27f)

Features

Add favicon option (#1207) (5b045f2)

9.1.1 (2018-12-21)
Bug Fixes

inferred properties duplicating explicitly specified ones (2d0bd0e)

v9.1.0
Compare Source
Features

support spead types (ca5a681)

v9.0.0
Compare Source
Features

support spead types (ca5a681)

rollup/rollup
v1.25.2
Compare Source
2019-10-23
Bug Fixes

Improve performance of bundled UMD code by adding additional parentheses to enforce eager parsing (#3183)
Improve types to tolerate passing a Rollup config with multiple outputs to rollup.rollup (#3184)

Pull Requests

#3183: Add parentheses to factory function of UMD bundles (@ajihyf)
#3184: RollupOptions accept output as array (@imcotton)

v1.25.1
Compare Source
2019-10-20
Bug Fixes

Handle a situation where code was not included after a switch statement (#3178)
Handle a situation where code was not included after a do-while loop (#3180)
Do not fail if different outputs emit the same file (#3175)
Give access to the original acorn error for parse errors (#3176)

Pull Requests

#3175: Disable errors for duplicate emitted file names (@marijnh)
#3176: Add original parser error to rollup error; Update tests (@gribnoysup)
#3178: Fix switch case not being included correctly (@lukastaegert)
#3179: Update dependencies (@lukastaegert)
#3180: Handle conditional breaks in do-while loops with unconditional return (@lukastaegert)

v1.25.0
Compare Source
2019-10-18
Features

Remove try-catch if there is no side-effect in the try-block (#3166)
Omit side-effect-free trailing cases in switch-statements (#3166)
Remove unused labels (#3170)

Bug Fixes

Do not remove code after labeled statements that contain a throw or return if the label is used (#3170)
Prevent invalid code when expressions are simplified that do not follow a white-space character (#3173)
Do not remove continue statements inside switch statements (#3166)
Prevent trailing empty lines when tree-shaking inside switch statements (#3166)

Pull Requests

#3166: Better try statement tree shaking (@lukastaegert)
#3170: Handle optional control flow in labeled statements, remove unused labels (@lukastaegert)
#3173: Add missing spaces in certain statements and expressions to avoid invalid code (@lukastaegert)

v1.24.0
Compare Source
2019-10-15
Features

Respect break, continue, return and throw when tree-shaking to detect dead code (#3153)
Do treat treat hoisted function declarations as "unknown" when checking for call side-effects (#3153)

Bug Fixes

Make sure that unknown import.meta properties produce valid code in SystemJS (#3152)
Make sure treeshake.annotations: false is respected for class instantiation (#3153)
Check property access side-effects for class instantiation (#3153)
Do not suppress break statements inside labeled statements (#3153)

Pull Requests

#3152: Allow import.meta.* for systemjs format (@dmail)
#3153: Get rid of immutable.js and implement tree-shaking for broken control flow (@lukastaegert)

v1.23.1
Compare Source
2019-10-05
Bug Fixes

Fix a regression where the node types had a specific minimal version (#3143)

Pull Requests

#3143: Ensure that types packages have star version ranges (@lukastaegert)

v1.23.0
Compare Source
2019-10-03
Features

Add placeholders for extensions when preserving modules (#3116)

Pull Requests

#3116: Include extensions in preserveModules output filenames for scriptified assets (@Andarist)
#3142: Fix typo (@tu4mo)

v1.22.0
Compare Source
2019-09-29
Features

Add a new "hidden" sourcemap type that generates the map files but omits the sourcemap comment (#3120)
Generate more efficient code when using namespaceToStringTag: true (#3135)
Make sure namespace objects do not have a prototype (#3136)

Bug Fixes

Do not ignore side-effectful iterators by always preserving for..of loops for now (#3132)
Make sure --context is observed as a CLI option (#3134)
Do not require specific versions for @types dependencies (#3131)

Pull Requests

#3120: Generate sourcemaps but omit the comment (@rohitmohan96)
#3131: Use asterisk for @types/* dependencies (@frenzzy)
#3132: Preserve empty for...of loops (@imatlopez)
#3133: Update dependencies (@lukastaegert)
#3134: Wire up --context CLI flag (@tchetwin)
#3135: Remove Symbol polyfill in module namespaces (@mkubilayk)
#3136: Set null prototype on namespace objects (@rpamely)

v1.21.4
Compare Source
2019-09-16
Bug Fixes

Recognize common browser globals (#3117)
Do not treat "typeof " as a side-effect (#3117)

Pull Requests

#3117: Add browser globals to known globals and prevent "typeof" side-effects (@lukastaegert)

v1.21.3
Compare Source
2019-09-14
Bug Fixes

Fix a regression where modifying a watched file did not trigger a rebuild (#3112)

Pull Requests

#3112: Fix .addWatchFile() dependencies failing to invalidate in watch mode (@tivac)

v1.21.2
Compare Source
2019-09-09
Bug Fixes

Fix wrong deprecation message to direct to this.emitFile instead of this.emitAsset

v1.21.1
Compare Source
2019-09-09
Bug Fixes

Allow legacy plugins to still add assets directly to the bundle object (#3105)

Pull Requests

#3105: Allow legacy plugins to still add assets directly to the bundle object (@lukastaegert)

v1.21.0
Compare Source
2019-09-08
Features

Respect output.entryFileNames when preserving modules (#3088)
Make accessing unknown globals a side-effect unless this is deactivated via treeshake.unknownGlobalSideEffects (#3068)
Respect global objects when checking for pure global functions (#3068)
Introduce a type to more easily distinguish chunks and assets in the output bundle (#3080)

Bug Fixes

Recover in watch mode when the initial build fails (#3081)
Make sure output.strict is respected for SystemJS output (#3101)

Pull Requests

#3068: Make accessing unknown globals a side-effect (@lukastaegert)
#3080: OutputBundle Tagged union with 'type = chunk|asset' (@askbeka)
#3081: Watch files onbuild, even if build fails (@mhkeller)
#3088: Add support for entryFileNames pattern used in combination with preserveModules option (@Andarist)
#3101: Remove 'use strict'; from systemjs when strict=false (@askbeka)

v1.20.3
Compare Source
2019-08-28
Bug Fixes

Make sure file hashes change when a change of the naming pattern leads to a file name change of a dependency (#3083)
Fix several issues where reexporting an external "default" export could lead to invalid or incorrect code (#3084)

Pull Requests

#3078: Add github actions workflow config for windows (@shellscape)
#3083: Properly reflect dependency file names in hash (@lukastaegert)
#3084: Fix "default" reexport issues in non ESM/System formats (@lukastaegert)

v1.20.2
Compare Source
2019-08-25
Bug Fixes

Avoid an issue where circular namespace reexports would crash Rollup (#3074)

Pull Requests

#3077: Handle namespaces that reexport themselves (@lukastaegert)

v1.20.1
Compare Source
2019-08-22
Bug Fixes

Fix an issue where variable names inside dynamic import expressions were not rendered correctly (#3073)
Fix type definition to allow a single watcher config as well as an array (#3074)

Pull Requests

#3073: Fix wrong variable name in import expression (@lukastaegert)
#3074: Fixes type definition on watch and Watcher constructor (@MicahZoltu)

v1.20.0
Compare Source
2019-08-21
Features

Add augmentChunkHash plugin hook to be able to reflect changes in renderChunk in the chunk hash (#2921)

Bug Fixes

Do not mutate the acorn options object (#3051)
Make sure the order of emitted chunks always reflects the order in which they were emitted (#3055)
Do not hang when there are strings containing comment-like syntax in some scenarios (#3069)

Pull Requests

#2921: Add augmentChunkHash plugin hook (@isidrok)
#2995: Add info on installing locally to docs (@mesqueeb)
#3037: Refresh pull request labels (@shellscape)
#3048: Document ROLLUP_WATCH environment variable (@shellscape)
#3051: Avoid changes to the original options (.acorn) object (@LongTengDao)
#3052: Minor refactoring: Remove one try-catch (@KSXGitHub)
#3053: Refactor to use async-await in more places (@KSXGitHub)
#3055: Provide consistent chunking via a consistent order of entry modules when emitting chunks (@lukastaegert)
#3058: Remove acorn-bigint and acorn-dynamic-import from bundle (@LongTengDao)
#3061: Update to acorn@7 (@lukastaegert)
#3063: Auto-generate license file (@lukastaegert)
#3069: Prevent infinite loop when scanning for line-breaks and there are comment-like strings (@lukastaegert)

v1.19.4
Compare Source
2019-08-07
Bug Fixes

Prevent invalid code when exporting an external namespace (#3034)
Prevent invalid or non-equivalent code when simplifying expressions in return and throw statements (#3035)

Pull Requests

#3034: Avoid generating .* as export (@LongTengDao)
#3035: Prevent ASI errors for conditional expressions (@lukastaegert)
#3036: Fix documents to use https, not http (@giraffate)

v1.19.3
Compare Source
2019-08-06
Bug Fixes

Fix wrong URLs in error messages (#3033)

Pull Requests

#3033: Fix wrong URLs in error messages (@giraffate)

v1.19.2
Compare Source
2019-08-05
Bug Fixes

Add bin file to package

v1.19.1
Compare Source
2019-08-05
Bug Fixes

Remove wrong extension in package.json file (#3031)

Pull Requests

#3031: Fix wrong extension (@lukastaegert)

v1.19.0
Compare Source
2019-08-05
Features

Implement a new unified file emission API for assets and chunks with support for explicit file names (#2999)
Use the id of the last module in a chunk as base for the chunk name if no better name is available (#3025)
Use the id of the last module in a chunk as base for the variable name of a chunk in some formats if no better name is available (#2999)

Bug Fixes

Do not produce invalid variable names if an empty name is chosen for a virtual module (#3026)
Fix an issue where a module variable name would conflict with a local variable name in some formats (#3020)

Pull Requests

#2999: Unified file emission api (@lukastaegert)
#3020: Switch to a code-splitting build and update dependencies (@lukastaegert)
#3025: Use id of last module in chunk as name base for auto-generated chunks (@lukastaegert)
#3026: Avoid variable from empty module name be empty (@LongTengDao)

v1.18.0
Compare Source
2019-08-01
Features

Add externalLiveBindings: false option to optimize code when live bindings are not needed (#3010)

Pull Requests

#2997: Integrate coverage into CI setup (@lukastaegert)
#2998: Update readme badges (@lukastaegert)
#3010: Add option to prevent code for external live bindings (@lukastaegert)

v1.17.0
Compare Source
2019-07-15
Features

Allow plugins to access current combined sourcemap in transform hook for coverage instrumentation (#2993)

Pull Requests

#2987: Fix code fences for link (@johanholmerin)
#2989: Bump lodash from 4.17.11 to 4.17.14 (@dependabot)
#2993: Add getCombinedSourceMap in transform plugin context (@billowz)

v1.16.7
Compare Source
2019-07-09
Bug Fixes

Fix an issue where exported import.meta properties would lead to invalid code (#2986)

Pull Requests

#2985: Improve sourcemap types (@jridgewell)
#2986: Only overwrite content when resolving import.meta properties (@lukastaegert)

v1.16.6
Compare Source
2019-07-04
Bug Fixes

Do not pass undefined to resolveDynamicImport for unresolvable template literals (#2984)

Pull Requests

#2984: Always forward AST nodes for unresolvable dynamic imports (@lukastaegert)

v1.16.5
Compare Source
2019-07-04
Bug Fixes

onwarn should still be called when --silent is used (#2982)
Properly clean up watchers for files that are deleted between builds (#2982)

Pull Requests

#2981: Do not skip onwarn handler when --silent is used (@lukastaegert)
#2982: Make tests run on Node 12, fix watcher cleanup issue (@lukastaegert)

v1.16.4
Compare Source
2019-07-02
Bug Fixes

Do not show a TypeScript error when providing a location as number to this.warn and this.error (#2974)
Use the correct TypeScript type for Sourcemap.version (#2976)

Pull Requests

#2965: Use async readFile in getRollupDefaultPlugin (@kaksmet)
#2974: Align TS types, docs and implementation for this.warn and this.error (@lukastaegert)
#2976: Fix sourcemap type and update dependencies (@lukastaegert)

v1.16.3
Compare Source
2019-06-29
Bug Fixes

Prevent name conflicts with unused function parameters (#2972)

Pull Requests

#2972: Deconflict unused parameters (@lukastaegert)

v1.16.2
Compare Source
2019-06-22
Bug Fixes

Properly wrap dynamic imports in Promises that can be caught when generating CJS output (#2958)

Pull Requests

#2958: Make sure errors from dynamic imports can be caught (@lukastaegert)

v1.16.1
Compare Source
2019-06-21
Pull Requests

#2956: Add missing CLI docs for strictDeprecations (@lukastaegert)

v1.16.0
Compare Source
2019-06-21
Features

Add strictDeprecations option to throw when currently or upcoming deprecated features are used (#2945)
Keep annotations and comments when simplifying logical and conditional expressions (#2955)

Bug Fixes

Generate proper namespace objects when dynamically importing external dependencies for AMD or CJS formats (#2954)
Fix dynamically imported variables not being resolved correctly when importing from an entry chunk with only a default export (#2954)
Do not reexport default when reexporting a namespace (#2954)

Pull Requests

#2945: Add option to handle use of features marked for deprecation as errors (@lukastaegert)
#2954: Improve dynamic import interop (@lukastaegert)
#2955: Keep annotations and comments when simplifying logical and conditional expressions (@lukastaegert)

v1.15.6
Compare Source
2019-06-16
Bug Fixes

No longer use an alternate screen in watch mode to allow scrolling (#2942)
Prioritize non-external imports over external ones when resolving conflicting namespace re-exports (#2893)

Pull Requests

#2893: Improve handling of conflicting namespace exports (@aleclarson)
#2942: Get rid of alternate screen and simplify screen clearing (@lukastaegert)

v1.15.5
Compare Source
2019-06-14
Bug Fixes

Do not include any comments for completely tree-shaken files so that renderedLength === 0 is a reliable check (#2940)
Do not cause type errors when returning null from resolveId (#2941)

Pull Requests

#2940: Completely omit files that do not have any included statements (@lukastaegert)
#2941: Explicitly allow null as return value for various hooks (@lukastaegert)

v1.15.4
Compare Source
2019-06-14
Bug Fixes

Improve how asset and chunk URLs are resolved for UMD, IIFE and CJS output (#2937)

Pull Requests

#2937: Fix URL resolution to work when the current script contains query parameters (@lukastaegert)

v1.15.3
Compare Source
2019-06-13
Bug Fixes

Always reemit assets and chunks from cached transform hooks (#2936)

Pull Requests

#2936: Fix repeated re-emission of files emitted from a transform hook (@lukastaegert)

v1.15.2
Compare Source
2019-06-13
Bug Fixes

Make sure chunks emitted from transform hooks are also emitted for incremental builds in watch mode (#2933)

Pull Requests

#2933: Reemit chunks emitted from transform hooks (@lukastaegert)

v1.15.1
Compare Source
2019-06-11
Bug Fixes

Do not fail when reexporting variables in dynamic entry points from other chunks (#2928)

Pull Requests

#2928: Handle reexports from dynamic entries across chunk (@lukastaegert)

v1.15.0
Compare Source
2019-06-11
Features

Tone down try-catch deoptimization while maintaining polyfill support (#2918)

Bug Fixes

Handle feature detection with "typeof" for regular expressios (#2916)
Deoptimize '' + variable' type coercion as expression statement for feature detection (#2917)
Always observe argument side-effects when tree-shaking (#2924)

Pull Requests

#2916: Deoptimize typeof for regular expression literals to better support es6-shim (@lukastaegert)
#2917: Support implicit type coercion errors in es5-shim (@lukastaegert)
#2918: Deoptimize try-catch less radically (@lukastaegert)
#2924: Do not tree-shake arguments with side-effects (@lukastaegert)

v1.14.6
Compare Source
2019-06-10
Bug Fixes

Fix an issue where call arguments were not included in try statements (#2914)

Pull Requests

#2914: Properly include try statements for each pass when deoptimization is deactivated (@lukastaegert)

v1.14.5
Compare Source
2019-06-09
Bug Fixes

Keep external ids unmodified when using the object form of resolveId (#2907)
Cache dynamic import resolutions when using Rollup cache (#2908)
Keep all necessary parentheses when tree-shaking call arguments (#2911)

Pull Requests

#2906: Update dependencies (@lukastaegert)
#2907: Do not renormalize external ids when using the object form (@lukastaegert)
#2908: Cache dynamic ids if possible (@lukastaegert)
#2911: Fix treeshaken parameters around parentheses (@manucorporat)

v1.14.4
Compare Source
2019-06-07
Bug Fixes

Do not omit external re-exports for moduleSideEffects: false (#2905)

Pull Requests

#2905: Make sure external re-exports are included for moduleSideEffects: false (@lukastaegert)

v1.14.3
Compare Source
2019-06-06
Bug Fixes

Generate correct external imports when importing from a directory that would be above the root of the current working directory (#2902)

Pull Requests

#2902: Use browser relative path algorithm for chunks (@lukastaegert)

v1.14.2
Compare Source
2019-06-05
Bug Fixes

Prevent unnecessary inclusion of external namespace import in certain situations (#2900)

Pull Requests

#2900: Handle early bind for member expressions (@lukastaegert)

v1.14.1
Compare Source
2019-06-05
Bug Fixes

Fix an issue where try-statements were not included properly when a variable declared inside the statement was accessed outside it (#2898)
Fix an issue where await expressions were not included properly (#2899)

Pull Requests

#2898: Properly include try-catch-statements even if they have already been included in some way (@lukastaegert)
#2899: Fix unintended early return in await inclusion handling (@lukastaegert)

v1.14.0
Compare Source
2019-06-05
Features

Deoptimize code inside and called from try-statements for feature detection (#2892)
Tree-shake unused call arguments (#2892)

Pull Requests

#2892: Implement try-statement-deoptimization for feature detection, tree-shake unused arguments (@lukastaegert)

v1.13.1
Compare Source
2019-06-01
Bug Fixes

Avoid conflicts between top-level module, require etc. and CommonJS runtimes (#2889)

Pull Requests

#2888: Enable full TypeScript strict mode (@lukastaegert)
#2889: Protect all module globals for CJS output from being redefined (@lukastaegert)

v1.13.0
Compare Source
2019-05-31
Features

Omit exports and module from SystemJS wrapper if possible (#2880)
Try to use the first letters of names when mangling exports (#2885)

Bug Fixes

Avoid conflicts with local variables when using format specific globals to render dynamic imports and file URLs (#2880)
Do not produce undefined reexports when reexporting from entry points (#2885)

Pull Requests

#2880: Deconflict global variables used inside format-specific code (@lukastaegert)
#2885: Do not produce undefined reexports when reexporting from entry points and refactor chunk linking (@lukastaegert)

v1.12.5
Compare Source
2019-05-30
Pull Requests

#2884: Update pluginutils for new micormatch and reduced bundle size (@lukastaegert)

v1.12.4
Compare Source
2019-05-27
Bug Fixes

Show correct error stack trace for errors throw in "load" hooks (#2871)

Pull Requests

#2875: Mention subfolders in docs (@lukastaegert)
#2871: Reserve error stack information (@LongTengDao)

v1.12.3
Compare Source
2019-05-19
Bug Fixes

Prevent duplicate imports when exports are reexported as default exports (#2866)

Pull Requests

#2755: Enable TypeScript strictNullChecks (@edsrzf)
#2866: Properly deduplicate reexported default exports (@lukastaegert)

v1.12.2
Compare Source
2019-05-17
Bug Fixes

Do not fail when using clearScreen:false in watchMode (#2858)
Properly resolve star reexports when preserving modules (#2860)

Pull Requests

#2858: Declare processConfigsErr before use (@humphd)
#2860: Keep nested exports with preserveModules (@TomCaserta)
#2864: Cache transitive reexport detection (@lukastaegert)

v1.12.1
Compare Source
2019-05-16
Bug Fixes

Extend file name sanitation to also replace "?" and "*" e.g. when preserving modules with the updated commonjs plugin (#2860)
Do not ignore module transformer that return an empty string (#2861)

Pull Requests

#2860: Update to latest plugins and extend file name sanitation (@lukastaegert)
#2861: Allow transformers to return an empty string (@lukastaegert)

v1.12.0
Compare Source
2019-05-15
Features

Add treeshake.moduleSideEffects option to allow removing empty imports without a side-effect check (#2844)
Extend plugin API to allow marking modules as side-effect-free (#2844)
Extend this.resolve plugin context function with an option to skip the resolveId hook of the calling plugin (#2844)
Add isEntry flag to this.getModuleInfo plugin context function (#2844)
Distribute Rollup as optimized ES2015 code (#2851)

Pull Requests

#2844: Add options and hooks to control module side effects (@lukastaegert)
#2851: Switch to ES2015 output (@lukastaegert)

v1.11.3
Compare Source
2019-05-05
Bug Fixes

Quote es3 keywords in namespace objects (#2825)

Pull Requests

#2825: Add es3 support for namespace object import (@sormy)

v1.11.2
Compare Source
2019-05-04
Bug Fixes

Prevent a crash when handling circular namespace exports (#2836)

Pull Requests

#2836: Make sure circular export * from X does not stack overflow (@Swatinem)

v1.11.1
Compare Source
2019-05-04
Bug Fixes

Fix an issue where rendered exports were reported as "removed" in the bundle information (#2835)

Pull Requests

#2835: Fix removedExports to correctly track the exported item (@Swatinem)

v1.11.0
Compare Source
2019-05-03
Features

Add emitChunk plugin context function to emit additional entry chunks that can be referenced from the code (#2809)
Allow manualChunks to be a function (#2831)
Omit .js extensions in AMD imports to make sure an AMD baseUrl would work (#2809)
Automatically use the name of the imported module as a base for dynamically imported chunks (#2809)
Add resolveFileUrl plugin hook to replace resolveAssetUrl and handle emitted chunks as well (#2809)
Add resolve plugin hook to replace resolveId and isExternal that returns an object (#2829)
Allow resolveDynamicImport to return an {id, external} object to also resolve unresolvable dynamic imports to a module (#2829)

Bug Fixes

Do not create invalid code if a dynamic import contains nothing but reexports (#2809)
Do not fail if modules that define a manual chunk depend on each other (#2809)
Do not fail if a module that defines a manual chunk is the dependency of a module defining a different manual chunk (#2809)
No longer fail for unnamed duplicate entry points but combine them (#2809)
Always return string | null from this.resolveId even if some resolveId hooks return objects (#2829)
Show proper warnings when resolveDynamicImport resolves to a non-external module that does not exist (#2829)

Pull Requests

#2809: Add hook for dynamic entry chunk emission (@lukastaegert)
#2821: Fix syntax error in documentation (@FFxSquall)
#2829: Improve id resolution (@lukastaegert)
#2831: Allow manualChunks to be a function (@lukastaegert)
#2832: Improve generateBundle documentation (@lukastaegert)
#2833: Update dependencies (@lukastaegert)

v1.10.1
Compare Source
2019-04-19
Bug Fixes

Invalid options.format values will now trigger a helpful error (#2813)

Pull Requests

#2812: Minor documentation update (@dnalborczyk)
#2813: Catch invalid options.format values (@marijnh)
#2816: Update all dependencies to fix security issues (@lukastaegert)

v1.10.0
Compare Source
2019-04-11
Features

Improve generated code to polyfill import.meta.url (#2785)
Add plugin hook to configure handling of import.meta (#2785)
Improve generated code when accessing URLs of emitted assets (#2796)
Add plugin hook to configure the generated code when accessing URLs of emitted assets (#2796)

Bug Fixes

No longer resolve assets to their parent URL in some cases (#2796)

Pull Requests

#2785: Refactor handling of import.meta.url and add option to configure behaviour (@lukastaegert)
#2796: Improve and fix asset emission (@lukastaegert)

v1.9.3
Compare Source
2019-04-10
Bug Fixes

Simplify return expressions that are evaluated before the surrounding function is bound (#2803)

Pull Requests

#2803: Handle out-of-order binding of identifiers to improve tree-shaking (@lukastaegert)

v1.9.2
Compare Source
2019-04-10
Bug Fixes

Allowing replacing output.file with output.dir in the outputOptions hook (#2802)

Pull Requests

#2802: Observe modified output options in bundle.write (@lukastaegert)

v1.9.1
Compare Source
2019-04-10
Bug Fixes

Make sure inline comments in dynamic imports are preserved (#2797)

Pull Requests

#2797: Emit inline comments inside dynamic import (@manucorporat)

v1.9.0
Compare Source
2019-04-05
Features

Add built-in support for bigint (#2789)

Pull Requests

#2789: Ship with bigint support built-in (@danielgindi)
#2791: Use shared extractAssignedNames from rollup-pluginutils (@lukastaegert)
#2792: Test that rollup-plugin-commonjs works with preserveModules (@lukastaegert)

v1.8.0
Compare Source
2019-04-02
Features

Support module as alias for esm and commonjs for cjs to match Node (#2783)

Pull Requests

#2782: Inline interopDefault in config loading (@guybedford)
#2783: Support Node-style format aliases (@guybedford)

v1.7.4
Compare Source
2019-03-28
Bug Fixes

facebook/create-react-app
v3.2.0
Compare Source
v3.2.0 is a minor release that adds support for production profiling and ignoring TypeScript type errors to make migrating JavaScript projects to TypeScript easier. It also includes other minor bug fixes and documentation updates.
:rocket: New Feature

react-scripts

#7737 Support production profiling with React Developer Tools (@JacobMGEvans)

react-dev-utils, react-scripts

#6931 Adds TSC_COMPILE_ON_ERROR env var... (@kylebebak)

:bug: Bug Fix

react-scripts

#7754 Fix linting error when using rest props (@alexandrtovmach)

react-app-polyfill

#7205 Guard polyfills against window possibly being undefined (@jxom)

:nail_care: Enhancement

react-scripts

#7687 Use installing package manager in README (@ashr81)
#7755 Support setting baseUrl to root directory (@rovansteen)
#7530 only load eslint config when EXTEND_ESLINT environment variable is specified/ do not swallow eslint config errors (@n1ru4l)
#7742 set output.globalObject to 'this' (@kentcdodds)
#7721 Add "entrypoints" key to asset manifest (@samuelmeuli)
#7562 enable .eslintignore again (@igtm)

react-dev-utils

#6980 Stop hiding the column number of ESLint errors (@justingrant)

:memo: Documentation

#7302 docs: note that 2 to 3 migration may require deletion of node_modules (@kimpers)
#7757 Documentation typo fix: accessbile→accessible (@tomer)
#7601 [Documentation] Updated list of supported Jest config overrides (@neilbryson)
#7705 Update runtime chunk name separator in docs (@samuelmeuli)

:house: Internal

react-scripts

#7752 Fix wrong letter casing (@lewislbr)

react-dev-utils, react-scripts

#7707 Remove 'shortcut' link type before 'icon' (@lewislbr)

:hammer: Underlying Tools

react-scripts

#7729 Remove switch case (@andrelmlins)

Committers: 19

Alexandr Tovmach (@alexandrtovmach)
André Lins (@andrelmlins)
Ashrith Reddy (@ashr81)
Federico Zivolo (@FezVrasta)
Iguchi Tomokatsu (@igtm)
Jacob M-G Evans (@JacobMGEvans)
Jake Moxey (@jxom)
Justin Grant (@justingrant)
Kent C. Dodds (@kentcdodds)
Kim Persson (@kimpers)
Kyle Bebak (@kylebebak)
Laurin Quast (@n1ru4l)
Lewis Llobera (@lewislbr)
Rakan Nimer (@rakannimer)
Reece Dunham (@RDIL)
Robert van Steen (@rovansteen)
Samuel Meuli (@samuelmeuli)
Tomer Cohen (@tomer)
neilbryson (@neilbryson)

Migrating from 3.1.2 to 3.2.0
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@3.2.0

or
yarn add --exact react-scripts@3.2.0

v3.1.2
Compare Source
v3.1.2 is a maintenance release that includes minor bug fixes and documentation updates.
:bug: Bug Fix

react-scripts

#7679 Change runtime chunk name separator from tilde to dash (@javadoug)
#7538 Explicitly checking that EXTEND_ESLINT is true (@BrockWills)

babel-preset-react-app, react-error-overlay, react-scripts

#7662 Fix build (@ianschmitz)

:nail_care: Enhancement

react-scripts

#7704 Add new logo (@iansu)
#7587 Minor performance improvements (@deftomat)
#7633 Disable babel-loader's cacheCompression (@jleclanche)

:memo: Documentation

#7616 Update deployment.md with another AWS example (@AndrewBestbier)
#7663 Remove --single-quote from prettier examples (@brlewis)
#7659 Update running-tests.md (@weyert)
#7459 Update troubleshooting.md (@prevostc)
#7650 Adopt Contributor Covenant (@iansu)
#7620 cleanup-after-each is no longer necessary! (@iHmD)
#7613 Fix seams between changelog majors (@emilpalsson)
#7368 Correcting proxy sample (@szabolcs-szilagyi)
#7536 add a migration step to remove static from robots.txt (@lookfirst)
#7521 Show logo for mobile views in create-react-app.dev (@GrooChu)

:house: Internal

react-scripts

#7526 The variable dotenvFiles is never reassigned - use const instead (@Primajin)
#7585 remove trailing spaces (@xiaoxiangmoe)

:hammer: Underlying Tools

babel-plugin-named-asset-import, confusing-browser-globals, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts

#7681 Bump dependencies (@ianschmitz)

react-scripts

#7531 Upgrade dotenv-expand to fix issues (@DominicTobias)

eslint-config-react-app, react-scripts

#7540 Bump version of @typescript-eslint/* (@pierreneter)

Committers: 20

Andrew (@AndrewBestbier)
Brock Wills (@BrockWills)
Clément Prévost (@prevostc)
Dominic Tobias (@DominicTobias)
Doug Ross (@javadoug)
Emil Pålsson (@emilpalsson)
Federico Zivolo (@FezVrasta)
Ian Schmitz (@ianschmitz)
Ian Sutherland (@iansu)
Jannis Hell (@Primajin)
Jerome Leclanche (@jleclanche)
Jon Stevens (@lookfirst)
Sabesh Rajendran (@GrooChu)
Tomáš Szabo (@deftomat)
Weyert de Boer (@weyert)
ZHAO Jinxiang (@xiaoxiangmoe)
@brlewis
@iHmD
@pierreneter
szabi (@szabolcs-szilagyi)

Migrating from 3.1.1 to 3.1.2
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@3.1.2

or
yarn add --exact react-scripts@3.1.2

v3.1.1
Compare Source
v3.1.1 is a maintenance release that includes minor bug fixes and documentation updates.
:bug: Bug Fix

react-scripts

#7513 Fix ESLint 6 support (@ianschmitz)
#7508 Don't block static files in robots.txt (@iansu)

:nail_care: Enhancement

eslint-config-react-app

#7393 Ignore "jsx-a11y/aria-role" for React components (@deftomat)

:memo: Documentation

#7527 Update Netlify config (@iansu)
#7500 Add links to Spectrum in README and docs (@iansu)

Committers: 3

Ian Schmitz (@ianschmitz)
Ian Sutherland (@iansu)
Tomáš Szabo (@deftomat)

Migrating from 3.1.0 to 3.1.1
Optionally remove Disallow: /static/ from public/robots.txt if you want to allow your images and other static files to be indexed by search engines #7508
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@3.1.1

or
yarn add --exact react-scripts@3.1.1

v3.1.0
Compare Source
v3.1.0 is a minor release that adds ESLint 6 support as well as experimental support for extended and customizing the ESLint config along with other minor bug fixes and documentation updates. The upgrade to ESLint 6 is a breaking change only if you're using eslint-config-react-app or react-error-overlay outside of Create React App.
v3.0.1
Compare Source
v3.0.1 is a maintenance release that adjusts some ESLint rules for TypeScript along with other minor bug fixes and documentation updates.
:boom: Breaking Change

babel-preset-react-app

#6887 Update dependencies of Babel preset with recent changes (@skoging)

:bug: Bug Fix

react-error-overlay, react-scripts

#7007 Unpin babel-jest (@ianschmitz)
#7002 Temporary fix for babel-jest preflight error (@ianschmitz)

eslint-config-react-app

#6987 Disable no-dupe-class-members rule for TypeScript (@ianschmitz)
#6862 Fix no-useless-constructor rule in TypeScript (@ianschmitz)

eslint-config-react-app, react-scripts

#6937 Disable default-case lint rule for TypeScript (@ianschmitz)

react-dev-utils

#6876 Change cssmodule classname hash to use relative paths (@vg-stan)

:nail_care: Enhancement

react-dev-utils, react-scripts

#6856 Adds the configuration for PnP/Typescript (@arcanis)

babel-preset-react-app

#6887 Update dependencies of Babel preset with recent changes (@skoging)

react-scripts

#6706 Generate SVG component name in Jest fileTransform (@dallonf)
#6300 Remove body padding reset from templates (@Hurtak)

:memo: Documentation

Other

#6979 Add note to restart the dev server after changing .env file (@MostafaNawara)
#6945 Add clarifying note to TypeScript docs warning about global install of CRA (@methodbox)
#6898 Update GraphQL docs (@nagman)
#6810 Call to action button now reacts to being hovered (@joerez)
#6881 Fix typo in deployment docs (@david-cho-lerat-HL2)

react-app-polyfill

#6879 Update README.md (@david-cho-lerat-HL2)

:house: Internal

react-scripts

#6854 Remove Object.assign from MiniCssExtractPlugin options (@swashcap)

Committers: 12

Chris Shaffer (@methodbox)
Cory Reed (@swashcap)
Dallon Feldner (@dallonf)
David Cho-Lerat (@david-cho-lerat-HL2)
Ian Schmitz (@ianschmitz)
Joe Rezendes (@joerez)
Maël Nison (@arcanis)
Mostafa Nawara (@MostafaNawara)
Petr Huřťák (@Hurtak)
Tore Hammervoll (@skoging)
@nagman
@vg-stan

Migrating from 3.0.0 to 3.0.1
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@3.0.1

or
yarn add --exact react-scripts@3.0.1

v3.0.0
Compare Source
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@3.0.0

or
yarn add --exact react-scripts@3.0.0

NOTE: You may need to delete your node_modules folder and reinstall your dependencies by running yarn (or npm install) if you encounter errors after upgrading.
If you previously ejected but now want to upgrade, one common solution is to find the commits where you ejected (and any subsequent commits changing the configuration), revert them, upgrade, and later optionally eject again. It’s also possible that the feature you ejected for is now supported out of the box.
Breaking Changes
Like any major release, react-scripts@3.0.0 contains a few breaking changes. We expect that they won't affect every user, but we recommend you look over this section to see if something is relevant to you. If we missed something, please file a new issue.
Jest 24
We've updated from Jest 23 to get the latest improvements in Jest 24. We've noticed some differences in snapshot serialization in Jest 24, so you may need to adjust your tests slightly once you update. You can read more about what's changed in the Jest 24 blog post.
Hooks support
We now enforce Rules of Hooks with eslint-plugin-react-hooks. If you are breaking any of the rules of Hooks this will cause your build to fail.
TypeScript linting
We now lint TypeScript files. You can see the list of rules we enforce to check if your project is compatible. If you're using Visual Studio Code you can follow our guide to setup up your editor to display lint warnings.
browserslist support in @babel/preset-env
The browserslist config in your package.json is now used to control the output of your JavaScript files. You can use separate configuration for development and production. See here for a good starting point which gives a good development experience, especially when using language features such as async/await, but still provides high compatibility with many browsers in production
Remove --no-watch flag
We've removed the --no-watch flag from the start script in favor of Jest's own --watchAll=false.
New structure in asset-manifest.json
All asset paths have been moved under the files key in asset-manifest.json.
New Features
using jsconfig.json/tsconfig.json
We now support setting baseUrl in jsconfig.json and tsconfig.json. To configure baseUrl to point to the src directory in your JavaScript project, create a jsconfig.json file in your project root:
{
  "compilerOptions": {
    "baseUrl": "src"
  },
  "include": ["src"]
}

If you have a TypeScript project you can configure baseUrl the same way in your tsconfig.json.
Currently the only supported options for baseUrl are node_modules (the default) and src.
PostCSS Normalize
You can now include a version of Normalize.css in your project that will use your browserslist setting to generate the appropriate styles for your target browsers. To include it simply add @import-normalize at the top of one of your CSS files.
v2.1.8
Compare Source
2.1.8 (March 7, 2019)
v2.1.8 is a maintenance release that reapplies the TypeScript speed improvements (#6406) in a new major version of react-dev-utils.
Migrating from 2.1.7 to 2.1.8
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@2.1.8

or
yarn add --exact react-scripts@2.1.8

v2.1.7
Compare Source
2.1.7 (March 7, 2019)
v2.1.7 is a maintenance release that temporarily reverts the TypeScript speed improvements (#6406) to fix a dependency issue in react-dev-utils.
Migrating from 2.1.6 to 2.1.7
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@2.1.7

or
yarn add --exact react-scripts@2.1.7

v2.1.6
Compare Source
2.1.6 (March 6, 2019)
v2.1.6 is a maintenance release that brings a few new improvements, most notably:

:rocket: Reduced TypeScript rebuild times while running the development server. This was previously introduced in v2.1.4 but had to be reverted. Thanks to @ianschmitz for getting this ready.

:bug: Bug Fix

react-dev-utils

#6511 Fix deploy instructions to make link clickable. (@sbimochan)

react-scripts

#6472 Revert CSS sourcemaps in development. (@bugzpodder)
#6444 Revert "Switch to eval-source-map (#5060)". (@ianschmitz)

:nail_care: Enhancement

react-dev-utils, react-scripts

#6406 Speed up TypeScript rebuild times in development. (@ianschmitz)

create-react-app

#6253 Only use yarn.lock.cached if using the default Yarn registry. (@hangryCat)

react-scripts

#5457 Add forward ref to React SVG Component. (@GasimGasimzada)

:memo: Documentation

babel-preset-react-app

#6254 Improve Flow and TypeScript usage docs. (@saranshkataria)

babel-preset-react-app, confusing-browser-globals, react-app-polyfill

#6419 Improve language used in markdown code blocks. (@cherouvim)

create-react-app

#6481 Fix typo. (@adyouri)

react-dev-utils

#6482 Fix typo. (@mattfwood)

Other

#6438 Update source-map-explorer docs to analyze all chunks. (@Kamahl19)
#6454 Fix typo. (@DenrizSusam)
#5767 Add information about using custom registries in e2e testing #4488. (@juanpicado)

react-dev-utils, react-scripts

#6239 Convert all bit.ly links from http to https. (@leighhalliday)

:house: Internal

#6493 Remove AppVeyor config files. (@iansu)
#6474 Remove latest Node version from Travis config. (@iansu)

:hammer: Underlying Tools

react-scripts

#6387 Use contenthash instead of chunkhash for better long-term caching. (@ianschmitz)

Other

#6365 Upgrade Docusaurus and enable new features. (@yangshun)

Committers: 15

Abdelhadi Dyouri (adyouri)
Bimochan Shrestha (sbimochan)
Deniz Susman (DenrizSusam)
Gasim Gasimzada (GasimGasimzada)
Ian Schmitz (ianschmitz)
Ian Sutherland (iansu)
Ioannis Cherouvim (cherouvim)
Jack Zhao (bugzpodder)
Juan Picado @jotadeveloper (juanpicado)
Leigh Halliday (leighhalliday)
Martin Litvaj (Kamahl19)
Matt Wood (mattfwood)
Meo H. (hangryCat)
Saransh Kataria (saranshkataria)
Yangshun Tay (yangshun)

Migrating from 2.1.5 to 2.1.6
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@2.1.6

or
yarn add --exact react-scripts@2.1.6

v2.1.5
Compare Source
2.1.5 (February 11, 2019)
v2.1.5 is a maintenance release that reverts the TypeScript speed improvements (#5903) to fix a dependency issue in react-dev-utils.
Migrating from 2.1.4 to 2.1.5
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@2.1.5

or
yarn add --exact react-scripts@2.1.5

v2.1.4
Compare Source
2.1.4 (February 10, 2019)
v2.1.4 is a maintenance release that brings a number of awesome improvements. A few notable ones include:

:rocket: Reduced TypeScript rebuild times while running the development server. TypeScript is now blazing fast! Special thanks to @deftomat and @johnnyreilly and the other contributors for their hard work on this. (#5903)
Jest type ahead support which provides a much nicer experience when filtering your tests using the Jest CLI (#5213)
And many more improvements!

:bug: Bug Fix

react-scripts

#6364 Use semicolons in the ProcessEnv interface. (@DominikPalo)
#6276 Prevent cursor events on app-logo svg. (@kostadriano)

:nail_care: Enhancement

react-scripts

#5213 Add Jest typeahead plugin. (@gaearon)
#5713 Sass source map for dev. (@zhuoli99)
#6285 Allow react-scripts test --no-watch. (@ricokahler)
#5060 Enable eval-source-map for firefox. (@jasonLaster)

react-dev-utils, react-scripts

#5903 Speed up TypeScript projects. (@deftomat)

:memo: Documentation

Other

#6383 Update docs links to prefer HTTPS for supported domains. (@ianschmitz)
#6062 [docs] Warn/clarify that env vars are NOT "SECRET". (@JBallin)
#6359 Update ZEIT Now deployment instructions. (@timothyis)
#6346 Minor issue in README.md. (@nathanlschneider)
#6331 Update docs to document --no-watch. (@ricokahler)
#6229 Update serve port flag and add example. (@lyzhovnik)
#6190 Updating updating-to-new-releases.md for users who installed CRA globally. (@carpben)
#6095 Changes to steps for publishing GitHub User Page. (@StevenTan)
#6157 Add note for global install of CLI. (@ianschmitz)
#6149 update link for difference between proposal stages. (@loveky)
#6141 Remove extra table cell. (@yangshun)

react-scripts

#6355 Make manifest.json description more generic. (@chrisself)

:house: Internal

Other

#6050 Fix e2e:docker failure with "access denied". (@jamesknelson)
#6179 Update local-test.sh to return test exit code. (@dallonf)
#6165 Fix CI builds. (@ianschmitz)

react-scripts

#5798 Added module to ignored node modules list. (@dotansimha)
#6022 TypeScript detection filtering 'node_modules'.. (@holloway)

react-dev-utils, react-scripts

#6150 dependencies: move chalk to react-dev-utils. (@otaviopace)

babel-plugin-named-asset-import, react-scripts

#5816 Upgrade @svgr/webpack to 4.1.0. (@alaycock)

react-dev-utils

#6162 Update react-dev-util globby dependency to v8.0.2. (@davidlukerice)

babel-preset-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts

#6137 Fix CI and upgrade dependencies. (@Timer)

:hammer: Underlying Tools

babel-preset-react-app, react-app-polyfill, react-dev-utils, react-scripts

#6393 Upgrade dependencies. (@ianschmitz)

babel-preset-react-app

#6307 Update babel-plugin-macros 2.4.4 -> 2.4.5. (@maniax89)

eslint-config-react-app, react-scripts

#6132 Bump eslint-plugin-react version and update webpack config. (@ianschmitz)

Committers: 29

Adam Laycock (alaycock)
Adriano Costa (kostadriano)
Andrew Turgeon (maniax89)
Ben Carp (carpben)
Charles Pritchard (Downchuck)
Chris Self (chrisself)
Dallon Feldner (dallonf)
Dan Abramov (gaearon)
David Rice (davidlukerice)
Dominik Palo (DominikPalo)
Dotan Simha (dotansimha)
Ian Schmitz (ianschmitz)
JBallin (JBallin)
James George (jamesgeorge007)
James K Nelson (jamesknelson)
Jason Laster (jasonLaster)
Joe Haddad (Timer)
Matthew Holloway (holloway)
Nathan Schneider (nathanlschneider)
Nikita Lyzhov (lyzhovnik)
Otávio Pace (otaviopace)
Rico Kahler (ricokahler)
Steven Tan (StevenTan)
Timothy (timothyis)
Tomáš Szabo (deftomat)
Yangshun Tay (yangshun)
gottfired
zhuoli99
loveky (loveky)

Migrating from 2.1.3 to 2.1.4
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@2.1.4

or
yarn add --exact react-scripts@2.1.4

v2.1.3
Compare Source
2.1.3 (January 4, 2019)
v2.1.3 is a maintenance release to fix a vulnerability in webpack-dev-server.
:memo: Documentation

Other

#6067 Correct an error for documentation. (@hardo)
#6110 Replace deprecated VSCode launch.json variable. (@raiskila)
#5631 Generalize the adding bootstrap documentation. (@jquense)
#6084 Remove outdated docs for setting up eslint in editor. (@LukasWerfel)
#6061 Fix control comment of CSS Grid prefixing. (@denexapp)

react-scripts

#6036 Fix comment typo. (@shawtung)

:house: Internal

create-react-app, react-error-overlay

#6104 Typo fixes. (@prashant-andani)

:hammer: Underlying Tools

react-scripts

#6064 Update webpack-dev-server 3.1.9 -> 3.1.14. (@Friss)

Committers: 8

Denis Mukhametov (denexapp)
Hardo (hardo)
Janne Raiskila (raiskila)
Jason Quense (jquense)
Lukas Werfel (LukasWerfel)
Prashant Andani (prashant-andani)
Zachary Friss (Friss)
shawtung

Migrating from 2.1.2 to 2.1.3
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@2.1.3

or
yarn add --exact react-scripts@2.1.3

v2.1.2
Compare Source
2.1.2 (December 23, 2018)
v2.1.2 is a maintenance release including various bug fixes.
:rocket: New Feature

babel-preset-react-app

#5487 Add allowESModules option to babel-preset-react-app (@Pajn)

:bug: Bug Fix

create-react-app

#5905 Disable copy to clipboard in create-react-app --info (@heyimalex)
#5685 Update envinfo to 5.11.1 (@tabrindle)

babel-preset-react-app

#5783 Fix TypeScript decorator support (@ianschmitz)

babel-plugin-named-asset-import

#5573 Fix named-asset-import plugin to work with export-as syntax (@NShahri)

react-app-polyfill

#5789 Don't polyfill fetch for Node (@gshilin)

react-scripts

#5721 Version bump postcss-preset-env to latest (@BPScott)
#5701 Fix tsconfig.json lib suggested value (@ianschmitz)

:nail_care: Enhancement

react-scripts

#5698 Add support for setupTests.ts (@ianschmitz)

:memo: Documentation

Other

#6009 Correct markdown to avoid comment. (@souzasmatheus)
#6015 Add example command to create typed project. (@mbelsky)
#6000 Make links to docs consistent in README. (@iansu)
#5900 Add production build section to docs. (@ianschmitz)
#5985 Use https for linked images to fix mixed content warnings. (@iansu)
#5919 Docs: update localStorage mock in “Running Tests”. (@phacks)
#5917 Add SASS_PATH instructions to Sass stylesheet docs. (@jayantbh)
#5823 Add default values to file_ext note. (@alaycock)
#5907 Update README.md with updated link about PWAs. (@wuweiweiwu)
#5858 Some Grammar fixes. (@nikhilknoldus)
#5883 Fix link to page about running tests. (@wsmoak)
#5849 React native repository updated in README.md. (@pavinthan)
#5806 Rename 'getting started' link to 'docs'. (@kulek1)
#5788 docs: Simplify installing Storybook with npx (@sagirk)
#5779 docs: Change story book command to sb init (@andys8)
#5759 Add PR welcoming badge (@open-source-explorer)
#5730 Suggest Encore when not building a SPA with Symfony (@dunglas)
#5710 Updated the link to firebase hosting (@githubsaturn)
#5704 Fixed link to manifest.json file (@m4jing)
#5670 Fix public folder documentation link (@makovkastar)

eslint-config-react-app

#5990 Updated docs for .eslintrc (@ManoelLobo)

babel-preset-react-app, create-react-app, eslint-config-react-app, react-dev-utils, react-scripts

#5912 Update links to docs in all package README files (@iansu)

react-scripts

#5974 Improve advice in verifyPackageTree.js (@sjalgeo)
#5954 Add pre-eject message about new features in v2 (@iansu)
#5808 Add placeholders to template README for bit.ly links (@iansu)

react-app-polyfill

#5814 Note that extra polyfills must be included manually (@ajwann)

babel-preset-react-app, eslint-config-react-app, react-error-overlay, react-scripts

#5727 Fix typo (@noelyoo)

:house: Internal

react-scripts

#5978 Add webp support for TypeScript. (@dugagjin)
#5959 Suggest a different default for speed reasons. (@Timer)
#5839 Run prettier on HTML files. (@sibiraj-s)
#5722 Merge webpack configuration. (@Timer)
#5694 Add permissive TS lib defaults. (@Timer)

Other

#5988 Added extension to .eslintrc (@ManoelLobo)
#5546 Add the latest stable node version. (@noelyoo)

react-dev-utils

#5927 Correct some comments. (@mjackson)
#5879 fix: make typescriptformatter support 0.5 of fork checker. (@SimenB)

react-error-overlay

#5451 fix: add sideEffects: false to react-error-overlay. (@SimenB)

babel-preset-react-app

#5487 Add allowESModules option to babel-preset-react-app. (@Pajn)

create-react-app

#4605 ignore intellij module files when generating an app. (@denofevil)

Committers: 36

\<Explorer /> (open-source-explorer)
Adam Laycock (alaycock)
Adam Wanninger (ajwann)
Alex Guerra (heyimalex)
Andy (andys8)
Ben Scott (BPScott)
Dennis Ushakov (denofevil)
Dugagjin Lashi (dugagjin)
Gregory Shilin (gshilin)
Ian Schmitz (ianschmitz)
Ian Sutherland (iansu)
Jayant Bhawal (jayantbh)
Jing Ma (m4jing)
Joe Haddad (Timer)
Kasra Bigdeli (githubsaturn)
Kévin Dunglas (dunglas)
Manoel (ManoelLobo)
Matheus Souza (souzasmatheus)
Max Belsky (mbelsky)
Michael Jackson (mjackson)
Nicolas Goutay (phacks)
Nikhil (nikhilknoldus)
Nima Shahri (NShahri)
Noel Yoo (noelyoo)
Oleksandr Melnykov (makovkastar)
Pavinthan (pavinthan)
Rasmus Eneman (Pajn)
Sagir Khan (sagirk)
Sibiraj (sibiraj-s)
Simen Bekkhus (SimenB)
Stephen Algeo (sjalgeo)
Trevor Brindle (tabrindle)
Wei-Wei Wu (wuweiweiwu)
Wendy Smoak (wsmoak)
kulek1
swyx (sw-yx)

Migrating from 2.1.1 to 2.1.2
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@2.1.2

or
yarn add --exact react-scripts@2.1.2

v2.1.1
Compare Source
2.1.1 (October 31, 2018)
Happy Halloween 🎃 👻! This spooky release brings a treat: decorator support in TypeScript files!
:bug: Bug Fix

babel-preset-react-app

#5659 Add support for decorators. (@Timer)

react-scripts

#5621 fix 'Duplicate string index signature' in ProcessEnv. (@xiaoxiangmoe)

:nail_care: Enhancement

babel-preset-react-app

#5659 Add support for decorators. (@Timer)

:memo: Documentation

#5658 Update making-a-progressive-web-app.md. (@jakeboone02)
#5635 Update minimum node version to 8.10 in README. (@iansu)
#5629 Add link to cra-ts migration guide. (@Vinnl)

:house: Internal

react-error-overlay

#4709 Expose reportRuntimeError. (@hipstersmoothie)

babel-plugin-named-asset-import

#5575 add tests for named-asset-imports plugin. (@NShahri)

react-scripts

#5651 Make serviceWorker config argument optional in typescript. (@eddedd88)

Committers: 8

Andrew Lisowski (hipstersmoothie)
Eduardo Duran (eddedd88)
Ian Sutherland (iansu)
Jake Boone (jakeboone02)
Joe Haddad (Timer)
Nima Shahri (NShahri)
Vincent (Vinnl)
ZHAO Jinxiang (xiaoxiangmoe)

Migrating from 2.1.0 to 2.1.1
Inside any created project that has not been ejected, run:
npm install --save --save-exact react-scripts@2.1.1

or
yarn add --exact react-scripts@2.1.1

v2.1.0
Compare Source
2.1.0 (October 29, 2018)
Create React App 2.1 adds support for TypeScript! Read the documentation to get started.
New applications can be created using TypeScript by running:
$ npx create-react-app my-app --typescript

:rocket: New Feature

create-react-app, react-scripts

#5550 Add TypeScript app creation (@Timer)

babel-preset-react-app, react-scripts

#4837 TypeScript support using Babel 7 (@brunolemos)

:bug: Bug Fix

react-scripts

#5611 Remove react-scripts type reference on eject. (@Timer)
#5614 Ignore json files from TypeScript type checking. (@brunolemos)
#5609 Remove unsupported options. (@Timer)
#5608 Ignore test files from reported type errors. (@Timer)
#5589 Update react-app.d.ts. ([@brunolemos](https://togithub.com/brunol

This PR has been generated by Renovate Bot. View repository job log here.

:tada: This pull request is included in v2.3.0, available on npm: draftjs-filters@2.3.0.

Generated by :package::rocket: semantic-release

repo: thibaudcolas/draftjs-filters


text:
No such module 'FontAwesome'

I get the error' No such module FontAwesome' after both trying to install FontAwesome.swift with cocoapods and manually.

import FontAwesome_swift

@nferruzzi

import FontAwesome_swift
yeah, i tried that and import FontAwesome

@heyitswither It works for us though. Could you share a sample project which reproduces the error?

@thii i will get one in a few hours

source: gharchive/issue

authors: heyitswither nferruzzi thii

license: mit

license_type: permissive

license_source: bigquery


text:
test(thirdweb): add condition to serialize-transaction eip1559 test based on TW_SECRET_KEY

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR focuses on adding a conditional test for the "eip1559" function based on the presence of a secret key.
Detailed summary

Added a conditional test for the "eip1559" function based on the presence of a secret key.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#3955  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gregfromstl and the rest of your teammates on  Graphite

source: gharchive/pull-request

repo: thirdweb-dev/js

license_source: github-api


text:
Add Description Field

I could not imagine using Fusion without this plugin. What a time saver. We started making drawings and find the "description" field important but there is no name in there....Is it possible to add this to DirectName?

Hi, I have not used the Drawings environment that much. Could you provide some screenshots of this field and also when you expect DirectName to pop up?
Don't keep your hopes up though. Except for the Design workspace, the Fusion support for add-ins is very limited.

Hi,
I imagined that the "Description" field would added to the DirectName
prompt in the design workspace. As of now in Fusion, the Description field
can only be accessed Select Component, Right click, Properties. Since I
type the name of the feature once and copy and paste it for body name and
description, It would be so convenient if it could happen all in one place.
The description field change made in the design workspace gets pushed to
the drawing workspace.
See screenshots.
Best, Troy
On Sat, Jan 28, 2023 at 7:40 AM Thomas Axelsson @.***>
wrote:

Hi, I have not used the Drawings environment that much. Could you provide
some screenshots of this field and also when you expect DirectName to pop
up?
Don't keep your hopes up though. Except for the Design workspace, the
Fusion support for add-ins is very limited.
—
Reply to this email directly, view it on GitHub
https://github.com/thomasa88/DirectName/issues/4#issuecomment-1407310486,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQDJQKR34HZJU5LQZ6MSCCTWUS5O5ANCNFSM6AAAAAAUJOOY6A
.
You are receiving this because you authored the thread.Message ID:
@.***>

Code note: Field: component.description

Hi, I just published version 1.4.1 on Github, where I have added this feature. A new installer will hopefully appear in the Autodesk app store in 1-2 weeks.

license: MIT


text:
Investigate various changes to transaction panel

Currently when interacting with the transactions slide panel there seem to be some inconsistencies like some values populating and some not in the edit form.

Issues were arising when the same view was reloaded but the component didn't detect prop changes this was fixed with a componentDidUpdate lifecycle hook


text:
Bad axis scale for power (cycling) in Recent Efforts est. power graph

Fixes the issue of power axis scale in Recent Efforts est. power graph wrong when HR data were missing for the last ride.

:)

authors: OndrejSpanel thomaschampagne

repo: thomaschampagne/stravistix


text:
🛑 humite.stewarts.org.uk ssh is down

In 7350147, humite.stewarts.org.uk ssh (humite.stewarts.org.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: humite.stewarts.org.uk ssh is back up in cc8b2d4 after 11 minutes.

repo: thomasdstewart/upptime


text:
🛑 Portainer-NBG is down

In aa5e487, Portainer-NBG ($URL_PORTAINER_DE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portainer-NBG is back up in 8830a8a.

RCA: https://github.com/upptime/upptime/issues/319

repo: thomasmerz/upptime


text:
🛑 Portainer-NBG is down

In 8cd68cd, Portainer-NBG ($URL_PORTAINER_DE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portainer-NBG is back up in e393d3b after 9 minutes.


text:
🛑 Syncthing-NBG is down

In b920165, Syncthing-NBG ($URL_SYNCTHING_HETZNER_CLOUDSERVER_DE) was down:

HTTP code: 0
Response time: 0 ms

Already UP again since https://github.com/thomasmerz/upptime/commit/febba9001ed0f6d3654ba8e8b759cbd27458982e - but this issue didn't get closed 😞


text:
🛑 Syncthing-NBG is down

In 3d6f4ab, Syncthing-NBG ($URL_SYNCTHING_HETZNER_CLOUDSERVER_DE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Syncthing-NBG is back up in b4c107a.


text:
🛑 Registry is down

In 6440d0b, Registry (https://registry.codifi.nl) was down:

HTTP code: 500
Response time: 77 ms

Resolved: Registry is back up in bc230de after 2 hours, 8 minutes.


text:
build homebrew recipe for sqlitebiter on macos

https://brew.sh/

Thank you for your suggestion.
I had added the Homebrew installation for macOS: https://github.com/thombashi/sqlitebiter/blob/master/docs/pages/installation.rst#installation-for-macos-via-homebrew

wow, thank you so much!

I'll close the issue.
Thanks.

authors: thombashi wingsuitist

repo: thombashi/sqlitebiter


text:
Curried functions to be removed in a later version of Swift

Greetings.
Presently, I'm implementing Runes like so in my app:
import Argo
import Runes

public struct Product {
    public let name: String
    public let price: NSDecimalNumber
    public let code: String
    public let balanceIncrease: Double?
    public let discount: NSDecimalNumber?

    public init(name: String, price: NSDecimalNumber, code: String, balanceIncrease: Double?, discount: NSDecimalNumber?) {
        self.name = name
        self.price = price
        self.code = code
        self.balanceIncrease = balanceIncrease
        self.discount = discount
    }
}

extension Product: Decodable {
    private static func create(name: String)(price: NSDecimalNumber)(code: String)(balanceIncrease: Double?)(discount: NSDecimalNumber?) -> Product {
        return Product(name: name, price: price, code: code, balanceIncrease: balanceIncrease, discount: discount)
    }

    public static func decode(json: JSON) -> Decoded<Product> {
        return Product.create
            <^> json <| "name"
            <*> json <| "price"
            <*> json <| "code"
            <*> json <|? "balance_increase"
            <*> json <|? "discount"
    }
}

extension Product: Equatable { }
public func ==(lhs: Product, rhs: Product) -> Bool {
    return lhs.name == rhs.name && lhs.price == rhs.price && lhs.code == rhs.code && lhs.balanceIncrease == rhs.balanceIncrease
}

extension Product: CustomStringConvertible {
    public var description: String {
        return "Product <name: \(self.name), price: \(self.price), code: \(code), balanceIncrease: \(balanceIncrease)>"
    }
}

But in extension Product: Decodable I am making use of curried functions to achieve what I need. Apparently curried syntax is being removed, so going forward, would you have any suggestions on how I would achieve similar results without function currying?

currying isn't being removed, the implicit currying syntax is being removed. I'd suggest using Curry.framework, or re-writing your create function to use an explicit curried syntax (see Curry.framework for examples on what that looks like).
Also, fwiw, you don't actually need Runes for Argo anymore, if that's the only place you're using it. We removed the hard dependency on Runes in Argo 2.0

Sorry for the duplicate posts -- my bad. Interesting. I will look into that. Thank you for the advice :+1:

No worries! Please let me know if you need any more guidance on this. I'm going to close this thread, but feel free to continue using it to ask questions.

I'm having a hard time picturing how this will look actually. Would it possible for you to show me an example using Curry that relates to my current code so I might apply it elsewhere in our project? I am not the original author and the original author is no longer available to contact unfortunately. :frowning:

Yep, no problem. It's a fairly straightforward change. You'd replace create with your default init method passed into curry. The full diff would look like this:
 import Argo
 import Runes
+import Curry

 public struct Product {
     public let name: String
     public let price: NSDecimalNumber
     public let code: String
     public let balanceIncrease: Double?
     public let discount: NSDecimalNumber?

     public init(name: String, price: NSDecimalNumber, code: String, balanceIncrease: Double?, discount: NSDecimalNumber?) {
         self.name = name
         self.price = price
         self.code = code
         self.balanceIncrease = balanceIncrease
         self.discount = discount
     }
 }

 extension Product: Decodable {
-    private static func create(name: String)(price: NSDecimalNumber)(code: String)(balanceIncrease: Double?)(discount: NSDecimalNumber?) -> Product {
-        return Product(name: name, price: price, code: code, balanceIncrease: balanceIncrease, discount: discount)
-    }
-
     public static func decode(json: JSON) -> Decoded<Product> {
-        return Product.create
+        return curry(Product.init)
             <^> json <| "name"
             <*> json <| "price"
             <*> json <| "code"
             <*> json <|? "balance_increase"
             <*> json <|? "discount"
     }
 }

Works like a charm and looks far more concise. You just saved the day! :tada: Thanks so much.

My pleasure! A couple other completely unsolicited notes (feel free to ignore if you already know any of this):

Like I mentioned before, I'd be willing to bet Runes can be removed as a dependency entirely, if you're on Argo 2.0+
It looks like you're marking everything as public and my assumption is that this is old code that needed to do this for the sake of unit testing. This isn't needed anymore, and you should be able to remove all instances of public from the code in your app bundle, using @testable import in your tests instead.
If you can remove public as noted above, then you can also remove the explicit initializer. Structs get an initializer identical to that automatically. That'll make this type even more concise, and reduce another place that you'd need to duplicate your type info.

repo: thoughtbot/Runes


text:
Add Bamboo.Phoenix.put_layout that accepts an atom for the template name

And use it for both the html and text layouts so you don't need to call put_text_layout and put_html_layout

@anellis This is a smaller one that could be useful. Right now we have functions for put_text_layout and put_html_layout. I'd also love to have put_layout(emails, {MyApp.LayoutView, :email.html})
This would basically call
email
|> Bamboo.Phoenix.put_text_layout({layout, to_string(template) <> ".text")
|> Bamboo.Phoenix.put_html_layout({layout, to_string(template) <> ".html")

Might be a good started task if you're interested!

@paulcsmith Awesome! I'll take a look and let you know if I have any questions

authors: anellis paulcsmith

repo: thoughtbot/bamboo


text:
Minimal setup instructions

Do the absolute minimum instead of everything.
Also don't require zsh 😄

Wrong app - meant to use our fork. SO SORRY!

repo: thoughtbot/laptop


text:
Conditionally create a module by using enabled variable

This is basically to add enabled = true/false variable so that we have a way to conditionally create a module or not when using threatstack module in another module.

Hi @bhegazy
Sorry for the delay on this, but what is the actual output if enabled is set to false? What are you hoping to gain by having the module in your terraform declarations, but not actually managing any resources?

Hi @olhado , Thanks for taking the time to review the PR, the purpose of this is when you use threatstack module inside another module we would like to conditionally set this variable to false ( for example no threatstack in staging account)
This means if we set enabled = false no resources will be created.
However this is not needed now, as of yesterday, Hashicorp released terraform version 0.13  which ships the ability to add count within a module, so I will be closing this PR

authors: bhegazy olhado

repo: threatstack/threatstack-terraform


text:
WIP: Update map_tree.py

Moving the roimap array as a table instead of being in the header when using HealpixMapROI.
The current patch can write hdf5 files now. Reading the HDF5 using the script hal_hdf5_to_fits.py gives a bit of problems since hal expects to read the roimap from the header. I'll see if this can be modified somehow.

I tested the changes using both HealpixROIMap and HealpixConeMap. I also used the script hal_hdf5_to_fits.py and it seems it works for both of them. I also noticed, although probably not that important, that tables 3.5.2 or bigger was needed. Maybe not necessary in py3.

@hayalaso  is this ready for review or are you still working on it?
Could you add something to the tests as well?

I got busy with other things the past couple of weeks so I  don't remember. I'll need to double-check.

Btw, on github, using WIP in the pull request name doesn't do anything. Instead, you can mark pull requests as draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/ You can also convert to draft later, there's a link on the upper right, underneath where you can select reviewers.

I added a test to write a model map using the HealpixROIMap and also read it back. I think it should be ready to merge.

Hi @hayalaso!
Thank you for implementing this!
Please pull in the most recent version of the hawc_hal master into your branch and resolve any conflicts. Note that the tests directory moved to hawc_hal/tests.
Once the tests pass, this is ready to merge.

Fixes #22
Fixes #55

authors: hayalaso henrikef


text:
Timeout reading from socket

with testnet and development branch
in CI got socket.timeout: timed out when trying to deploy vdc
full traceback
https://github.com/threefoldtech/js-sdk/runs/2625557889?check_suite_focus=true#step:6:57108

Github networking issue. seems to be resolved on the active PRs.

repo: threefoldtech/js-sdk


text:
threebot server start timeouts in new installations

When creating a new container with jsx container-install, then getting to a shell using jsx container-shell, then starting the threebot server using kosmos -p "j.servers.threebot.local_start_default()", it takes more time to start and sometime it times-out (even the server is still starting otther servers).
Tue 12 17:45:48 StartupCMD.py        - 276 - startupcmd_lapis                   : refresh: lapis
Tue 12 17:45:48 StartupCMD.py        - 301 - startupcmd_lapis                   : stop: lapis
^B^[[BTue 12 17:48:07 ot/ThreebotServer.py - 198 - start                              : EXCEPTION:
    Could not start threebot server
--TRACEBACK------------------
<string> in <module>
    1
/sandbox/lib/jumpscale/Jumpscale/servers/threebot/ThreeBotServersFactory.py in local_start_default
    61    client = self.default.start(background=True, web=web, timeout=timeout)
/sandbox/lib/jumpscale/Jumpscale/servers/threebot/ThreebotServer.py in start
    198    raise j.exceptions.Timeout("Could not start threebot server")
-----------------------------

Tue 12 17:48:08 BCDB.py              - 338 - bcdb                               : DATAPROCESSOR & SQLITE STOPPED OK

I figured out this only happen at first run because it tries to install too many dependencies using apt and pip.
Don't know if we can just increase the timeout  waiting for all other servers to start.

We also hit this problem for the deployement of 3bot using chatflow. This is blocking for the launch. needs to be fixed asap please.

yes, I faced this problem too. so we can increase threebot server timeout to 10 mins for the new installations. And this won't make a delay for the running machines.
PR: https://github.com/threefoldtech/jumpscaleX_core/pull/218

verified i, installation working well

jsx version

3BOTDEVEL:3bot:jumpscaleX_core: git log -1
commit 3e74acc8639dd5959ba320b0ac9bf33c0ee26648 (HEAD -> development, origin/development, origin/HEAD)
Author: Andrew Ayoub <andrew.a.mikhaeel@gmail.com>
Date:   Wed Nov 13 13:37:00 2019 +0200

    Development actor security (#205)

authors: AhmedHanafy725 Pishoy abom zaibon


text:
Development infradeployment

for issue https://github.com/threefoldtech/home/issues/549

Thank you!

authors: m-motawea ranatrk


text:
Question about encoding of leaves.

Docs state that leafs' address is given by hashing the key and hash of the value (hash(key ++ hash(value)) while in code its address is represented by hashing path to the leaf and its value hash. Which is true then?
If it's the latter - does it mean the same value will have a different leaf depending on its location within the trie? different location == different path == different hash.

The leaf format is key ++ hash(value) and the hash of the leaf is H(key ++ hash(value)).
KeyPath is actually the full key, not just the path to the particular leaf which commits to the key-value pair, so it doesn't vary as the leaf moves around in the trie.

authors: deuszx rphmeier

repo: thrumdev/nomt


text:
fix: stop split from creating too big right leaf

Another solution could be to find another LEAF_BULK_SPLIT_THRESHOLD but I couldn't find any value which was passing the tests introduced in #493, thus a recursive call to split was the easiest solution to cover this edge case

#492  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gabriele-0201 and the rest of your teammates on  Graphite

Yes, the branch updater should have the same problem. I was just focused on the leaf stage, so I pushed the fix and tests only for this. I will, of course, push it also for the branch in a following pr!


text:
Addition of temperature offset

Given that the thermal sensor is in the case, it is showing higher values than the room temp. Would it be possible to add an offset field to the plug-in to adjust the temp, keeping it in sync with the room temp.
Thanks!

??? The plug draws electricity, the temperature sensors are specifically for the temperature of the plug which changes based on power draw. Don't quite understand what you hope to achieve by offsetting it

With an offset option, this plug could be used to monitor room temperature when idle/switched off.

authors: snandor thunderbird


text:
Does returning things back to streamlit require an async function?

Heyo first just want to say this is a mega clutch addition to streamlit thank you for putting this together.
I was able to use this addon to get the end result I wanted (pass a JSON to a javascript function to restructure the JSON and return to streamlit), but I only seem to be able to get this to work if I leave everything inside the example await fetch() async function (the .then() method seems to run every line of code I throw inside it). Final step of my function does do a return, but I can't do this outside of a function and for some reason when I tried to just.. write a javascript function followed by calling that function, I wasn't getting anything back.
Here's an absolutely abysmal example:
# Does not work
def test(jsonstring):
   return st_javascript(f'''
        function fixjson(jsonstring) {{
            var obj = JSON.Parse(jsonstring);
            /* do a bunch of stuff to json */
            return obj;
        }};

        fixjson('{jsonstring}');
    ''')

st.write(test('{"test":"weeee"}'))

# Works
def test(jsonstring):
   return st_javascript(f'''await fetch("https://reqres.in/api/products/3").then(function(response) {{
            var obj = JSON.Parse('{jsonstring}');
            /* do a bunch of stuff to json */
            return obj;
        }});
    ''')

st.write(test('{"test":"weeee"}'))

I can understand how this would work if I was to just paste the whole thing into the javascript console in a web browser, but wondering if there's a better way to do this. Not the best at JS. Right now I'm... actually hitting the api for your example every time I try to run my streamlit app. That seems a little silly, and I'm sure there's a better way.
Cheers

Have a look at this. Solved my problem for me.

authors: Socvest chris-larsen


text:
解析单行注释的判断条件

在genAst.ts文件中，第166-167行中，单行注释的起始位置的判断似乎有问题，如果是# 这是一行注释这种情况，是不是就会被判断为非注释

if ( ['#', '/'].indexOf(code[offset + i++]) < 0 || (code[offset + i - 1] === '/' && code[offset + i++] !== '/')) {
    return false;
}


text:
🛑 MineCraft Gensoukyo is down

In d0665ff, MineCraft Gensoukyo (https://gensoukyo.moe/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MineCraft Gensoukyo is back up in 4e641c4 after 20 minutes.

repo: thwiki/status


text:
Fix GetPermissionsImplicitInternal() method, add tests for it.

Improved the stability of the method GetPermissionsImplicitInternal();
Added tests for this method.

Looks good to me, but I haven't gotten write access to these repos yet :).  I'll ask today.

authors: tdillenbeck vasylvasyliuk

repo: thycotic-rd/ladon


text:
Create a nix flake for reproducible development and build environments

This PR adds a nix flake definition, which provides as output a devshell, i.e. a development environment containing all necessary tools and libraries to work with bridle.
This (optionally) removes the dependency on any distribution packages installed via apt (or equivalent) apart from Nix itself, and removes the need for pip and virtualenv entirely.
To evaluate the flake, install Nix (the package manager), e.g. by apt install nix. Then either add experimental-features = nix-command flakes to ~/.config/nix/nix.conf, or add --experimental-features 'nix-command flakes' to any nix command.
After that, simply navigate to the bridle directory, and run nix develop to enter the devshell environment.
As a proof-of-concept, the PR also includes a subflake nix-workspace, which provides a fully fetched and initialized west workspace. This can be used to define derivations that include west commands, as demonstrated by the bridle-doc package also provided by the main flake. This makes it possible to generate the full documentation set by running nix build .#bridle-doc, also without installing any further dependencies or creating a local workspace.
This subflake is auto-generated via a python script, also currently located in nix-workspace. This script parses the project's west manifest and generates corresponding flake inputs, which can then be locked. Re-generating the subflake is only needed after manifest changes, otherwise upstream changes will be brought in via nix flake update as normal.
Note that the setup still suffers from an issue with subflakes, which requires building the required outputs from the subflake at least once to create a reference in the local nix store, before the main flake can reference it. In this case this means running nix build nix-workspace#workspace.

I've reworked this a bit, hopefully making it simpler to use and to understand.
All python dependencies are now collected in nix/python-dependencies.nix. Since a handful of packages in there aren't in nixpkgs, I've added basic derivations for them, also all found under nix/. These then get appended to the upstream package set so no additional special treatment is necessary.
I've also used the get-flake flake to make importing the workspace subflake much easier (no more explicitly building the package before using it!).
Both nix/python-dependencies.nix and nix/workspace/flake.nix can be re-generated by running west nix-update, which will also update the workspace subflake inputs, to make sure nix and west see the same upstream revisions. By running this after west update, the two should stay in sync.
Finally I've added a section to the documentation on how to start using the flake, although without going into detail on the underlying principles of nix and flakes (that is better explained elsewere, anyway).

In light of west2nix now being available, which in combination with pyproject2nix solves all these problems much more elegantly, I have reworked the flake to use those instead.
This has made things much simpler, since python dependencies are resolved directly from the requirements.txt, and the workspace can simply be locked into a west2nix.toml file with a single command, with no additional code generation.
I've also moved the additionally packaged python dependencies into an external repository, so updating them won't require action in this one.

repo: tiacsys/bridle


text:
Orden por ataque

Ordenar los pokemons por ataque.

Listo. #18


text:
🌐 Add German translation for docs/de/docs/how-to/graphql.md

← how-to/general.md (#10770)
→ how-to/custom-request-and-route.md (#10789)
German translation progress

📝 Docs preview for commit f2224cd970d98ca63b07af1e57d64df1b989a282 at: https://a909b4c5.fastapitiangolo.pages.dev

📝 Docs preview for commit 8fbad289f215f6845904addf9a0a220a59f39c3b at: https://ee04d12a.fastapitiangolo.pages.dev

📝 Docs preview for commit ee1f15dddbf59032d1b850528fff47fd1e151972 at: https://86ef136e.fastapitiangolo.pages.dev

📝 Docs preview for commit 495ed46ea9fd1a66388cd1fe473178b9398ce61f at: https://383f6e35.fastapitiangolo.pages.dev

📝 Docs preview for commit a37fd36c8ec6d3179e3f00bfd56b336068ba312e at: https://988df6fe.fastapitiangolo.pages.dev

Awesome @nilslindemann! :rocket:
As you are the champion of German translations and you have done so many, and with so much attention to detail, I'm gonna go ahead and merge this. :tada:
If others see things that could be improved later, we can check that in new PRs. :nerd_face:

authors: nilslindemann tiangolo

repo: tiangolo/fastapi


text:
Dynamically calculate paths based on latest props

The idea is to use function passed to decorator each time new props arrive to wrapped component.

@tiberiuc please review.

+1
@tiberiuc Is there anything missing to accept?

@prescottprue I believe https://github.com/prescottprue/redux-firebasev3 should be a fork of this repo as this will simplify applying patches back and forth and will look nicer in history later once it merged into mainline, what do you think?

@maxkomarychev There were a few people including myself that needed a new namespace for npm so that we could install the updated version for other projects. Instead of pointing to a forked repo in my package file, I copied over the repo (including history) into a new repo name.
I can merge changes from it back over to my fork of the library, just haven't had a reason to yet.
Feel free to post an issue on that repo about this if you want since this discussion no longer matches this issue.
Side Note: It looks like re-base now supports v3 of firebase

authors: maxkomarychev prescottprue

repo: tiberiuc/redux-react-firebase


text:
feat: [RJD-1199] add imu sensor to simple sensor simulator

Description
Abstract
Implement the feature to publish the IMU topic from scenario_simulator_v2
Details
This pull request implements the IMU sensor for the scenario_simulator_v2.
The following changes have been made:

Added ImuSensorBase and ImuSensor class to handle IMU data generation.
Updated SimulatorCore, SensorSimulation, and ScenarioSimulator classes to support the new IMU sensor.
Extended the ZeroMQ MultiClient and MultiServer classes to handle IMU sensor attachment requests.
Updated the proto schema to include ImuSensorConfiguration and related request/response messages.

Noise can be added to the IMU data if the add_noise_ flag is set.
Gravity can be added to the IMU data if the add_gravity_ flag is set.

References
Jira ticket: link
Destructive Changes
There are no destructive changes
Known Limitations
N/A

CI is green. It is ready for review


text:
改变文字小数位数

你好，我的项目里有不同的品种，小数位数从2-5位，源码在哪里改呢？

已找到方法

repo: tifezh/KChartView


text:
Remove 1's and I's from player codes

For fall term/v2.0, since it's a bit too late now.

Fixed in #90.

repo: tiffanynwyeung/uwhvz


text:
这是SKYLB么

rt

yes

偷偷关注

authors: mandarenmanman muziding wanghaibo

repo: tigcode/jupiter


text:
2.4.9版本升级到2.5.7版本奔溃

New Issue Checklist

[ ] I have read the Documentation
[ ] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
e.g. iOS / macOS

Platform Version
e.g.  10.15.7

TABAnimated Version
e.g. 2.5.7

Xcode Version
e.g. Xcode 11

由2.4.9版本升级到2.5.7 版本，直接报错。

我的代码里是有这个方法的，我的类名被修改了。找到了修改的版本记录。希望作者可以看一下

你这个方法不符合规范，2.4.9也会崩溃

我看了一下。2.4.9版本没有这块代码。这样它的类名变了，直接报找不到对应的代理方法了。我目前是用在UICollectionView里面然后用了一个LMJVerticalFlowLayout 做了一个瀑布流的布局，就出现这样找不到我瀑布流的代理方法了。

这代码是新增的，没有问题。
你这个瀑布流实现的selector不符合规范，旧的代码也会有问题。

这代码是新增的，没有问题。
你这个瀑布流实现的selector不符合规范，旧的代码也会有问题。

是这样的，瀑布流这个demo是新增的，我就必须写成TABAnimatedWaterFallLayout这样的，并完成一些代理。因为项目中以前写好了自己的flowLayout。所以我的项目是瀑布流的效果，但是不太想用瀑布流的骨架屏，想用正常collectionView 的骨架屏完成。这样好像不行，就会报出我第一次截图的错误。我这是瀑布流的布局，但依然还是想用正常collectionView的骨架屏是不行吗？

这代码是新增的，没有问题。
你这个瀑布流实现的selector不符合规范，旧的代码也会有问题。

瀑布流的关键代码是不是就是这几句。      CGFloat height = CardCollectionViewCell.cellSize.height;         NSArray <NSNumber *>* heightArray = @[@(height), @(height), @(height), @(height), @(height), @(height), @(height), @(height),@(height),@(height),@(height),@(height),@(height)];         TABCollectionAnimated *tabAnimated =         [TABCollectionAnimated animatedWaterFallLayoutWithCellClass:CardCollectionViewCell.class                                                         heightArray:heightArray                                                           heightSel:@selector(waterFallLayout:heightForItemAtIndex:itemWidth:)];
如果我目前是没有显示出来，我正在找原因，如果我是多个不同的cell 我应该怎么写。

这代码是新增的，没有问题。
你这个瀑布流实现的selector不符合规范，旧的代码也会有问题。

没有把代码全部过一遍，发现只要是瀑布流，好像就必须TABAnimatedWaterFallLayout 用这个，如果不配合试用的话，用自己写的UICollectionViewLayout 好像是不行的。确认下是不是这样的

没有这种说法，你在启动动画周期使用UICollectionFlowLayout就行
发自我的iPhone
------------------ 原始邮件 ------------------
发件人: weizhang @.>
发送时间: 2021年6月21日 16:57
收件人: tigerAndBull/TABAnimated @.>
抄送: tigerAndBull @.>, State change @.>
主题: 回复：[tigerAndBull/TABAnimated] 2.4.9版本升级到2.5.7版本奔溃 (#155)

没有这种说法，你在启动动画周期使用UICollectionFlowLayout就行 发自我的iPhone
…

我把你的demo里面的换掉

然后写了对应的代理。

就直接报错了

已沟通确认。
目前版本瀑布流实现的，返回高度的selector参数需要和demo上的一致，命名可以不同，否则会有这种情况。

authors: tigerAndBull weizhangCoder

repo: tigerAndBull/TABAnimated


text:
lsm: don't duplicate the entire CompactionInfo

CompactionInfo is stored by value by both pipeline slots and
compactions.
That is confusing! Given that the slot already has an index, it can use
that to fetch the info. But that's verbose, so let's duplicate just
compaction coordinates.

rebased&ready for review @cb22 !

repo: tigerbeetle/tigerbeetle


text:
Use lsof to better handle port info

Hi, this pull req solve in another way this problem: #87 (issue #58 )
Problem
Currently, if the connected database client is left open and a container is disabled, then the port is "read' as being in use.
Suggested Solution
Add a new method (portInfo($port)) to render process info with lsof.
lsof -n -P | grep -Ei 'ipv4.*:{$port}' |  tr -s ' ' | cut -d' ' -f1,2,3
New expectation
Inform which pid, process and user still using that port.

Closing per our conversation in #87 . We'll use netstat to check the ports. Thanks @danielebarbaro!

authors: danielebarbaro josecanhelp

repo: tighten/takeout


text:
Replace laracasts/TestDummy with Laravel Factories

Laravel 5 now includes its own way to prepare factories which makes this package no longer required. I'll be happy to update the tests, remove this package and submit a PR.

@mattstauffer would you it be easier for you if I submitted the changes to PR #229? or created a new PR?

@tomdiggle great question. I feel like we should separate it.

Ok, I'll submit a separate PR.

authors: mattstauffer tomdiggle

repo: tightenco/symposium


text:
copr: support cast enum to any type

What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
In pr https://github.com/tikv/tikv/pull/9648, it implements enum push down. But only implement cast enum to int/real/string. We need more types to support.
What is changed and how it works?
Proposal: xxx
What's Changed:
Related changes
Check List
Tests

Unit test
Integration test

Side effects
Release note

No release note.

/cc @skyzh @Xuanwo @dyzsr

Seems that write_enum_to_chunk is the same as write_enum. Is it necessary?

Only write_enum_to_chunk is ok.

/merge

repo: tikv/tikv


text:
import: log L0 SST ranges when too many files in ingest

Signed-off-by: lance6716 lance6716@gmail.com

What is changed and how it works?

Issue Number: Close #13980
What's Changed:

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

Unit test

Side effects
Release note
None

/cc @gozssky @lichunzhu

/cc @Connor1996

/cc @sticnarf

I don't know about the background. Do you already have some suspecion about what abnormal L0 SST ranges would look like and what can we do after we know the ranges?

I don't know about the background. Do you already have some suspecion about what abnormal L0 SST ranges would look like and what can we do after we know the ranges?

We suspect memtable covers a large range so a very "flat" SST file is flushed, blocking the futher ingestion. This PR want to print some clue about it, maybe we can see metaKV and rowKV is the start/end key of a SST file so indexKV ingestion is blocked.

/merge

/assign @sticnarf
no privilege, please help merge it

/cherrypick release-6.5


text:
txn: return duration_to_last_update when lock wait timeout

What is changed and how it works?

Issue Number: Close #14497
What's Changed:

When a timeout occurs during waiting for a lock, provide the duration of time that has passed since the last update of the lock wait.
Let the client decide whether it is necessary to resolve locks based on this info.

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

Manual test (add detailed scripts or steps below)

A single-row hot update workload
Left: this fix, right: master
Side effects

Performance regression

Consumes more CPU, in waiter manager

Release note
None

Signoff is missing on the commit eca2239, which causes the DCO check failure. Please fix that.

@ekexium lint failed

Sorry.. it seems that merging my another PR caused a conflict here... @ekexium

/merge

/merge

/test

/test

authors: MyonKeminta cfzjywxk ekexium


text:
upgrade lz4-sys to 1.9.4 to tackle security issue

What is changed and how it works?

Issue Number: Ref #15621
What's Changed:

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Release note
None

Cargo.lock cannot be manually updated. It's done automatically. @SpadeA-Tang

Cargo.lock cannot be manually updated. It's done automatically. @SpadeA-Tang

https://github.com/tikv/raft-engine/pull/338#discussion_r1325596256

/run-test retry=5

/run-test retry=7

/run-test retry=7

/merge

authors: SpadeA-Tang tonyxuqqi


text:
[DNM] Test Benchmark Infrastructure

This PR is used to test the stability of the benchmark infrastructure.

/bench +tpcc +sysbench +tpch

oh, amazing... how about /bench +all ?

@siddontang Good idea!

/bench +sysbench +tpch

authors: breeswish siddontang


text:
diff: /Podfile.lock: No such file or directory

Got this and have no clue to solve it out. Did anybody get the same issue before?

Then there's a problem with Cocoapods in your project.  Sometimes cocoapods can get out of sync and you need to re-initiate cocoapods. You should be able to resolve this error by:

Deleting the Podfile.lock file in your project folder
Deleting the Pods folder in your project folder
Execute 'pod install' in your project folder
Do a "Clean" in Xcode
Rebuild your project

I already tried it at the very beginning, but it didn't work out. Any other ideas?

@cbangchen
update your cocoapods to newest version
and run pod setup
and ..
Deleting the Podfile.lock file in your project folder
Deleting the Pods folder in your project folder
Execute 'pod install' in your project folder
Do a "Clean" in Xcode
Rebuild your project

@tilltue @fangyuxi, thx, update operation works.

solved for me: XCODE, IOS, CORDOVA y IONIC
1 - in xcode change value of $(SRCROOT) for you root project in xcode las var of config build in
2 - changed var in this clic in the plus of up: enter image description here
nota: root project is: location of my project and location where use pod this my firs question thank for watching
Images and details in:
https://stackoverflow.com/questions/40095677/how-can-i-add-a-symbol-like-srcroot-to-use-in-an-xcode-projects-build-settin/51971532#51971532

authors: cbangchen fangyuxi ivancho2802 tilltue

repo: tilltue/TLPhotoPicker


text:
helm_resource forces update by uninstalling release everytime

When releasing via helm_resource there should be an option available to not force an uninstall before deploying.
Looking at the output logs it is running upgrade --install during the release, hence the chart is always upgraded and if not present will be installed.
Add an option to disable/enable the force delete before deploy.

Can you give some repro steps?
As far as I can tell, helm upgrade --install does not do any force update / force delete. It diffs against what's installed and does a 3-way merge. if nothing has changed, nothing restarts.
I verified this with
git clone git@github.com:tilt-dev/tilt-extensions
cd tilt-extensions/helm_resource/test
tilt ci
kubectl get pods -lapp.kubernetes.io/name=memcached -o yaml | grep -e "resourceVersion"
tilt ci
kubectl get pods -lapp.kubernetes.io/name=memcached -o yaml | grep -e "resourceVersion"

and confirmed the pod didn't change

That would be the case is this was the only command that was run.
The following definition in my Tiltfile:
helm_resource(
  'oam-local',
  'oam/charts/oam-local',
  namespace='vela-system',
  resource_deps=['vela-core'],
  auto_init=False
)

causes the following output:
Web Trigger
STEP 1/2 — Force update
     Beginning force update
     Running cmd: python3 /Users/christian/.local/share/tilt-dev/tilt_modules/github.com/tilt-dev/tilt-extensions/helm_resource/helm-delete-helper.py

STEP 2/2 — Deploying
     Running cmd: python3 /Users/christian/.local/share/tilt-dev/tilt_modules/github.com/tilt-dev/tilt-extensions/helm_resource/helm-apply-helper.py
     Running cmd: ['helm', 'upgrade', '--install', '--namespace', 'vela-system', 'oam-local', 'oam/charts/oam-local']
     Release "oam-local" does not exist. Installing it now.
     NAME: oam-local
     LAST DEPLOYED: Wed Jun 28 17:15:12 2023
     NAMESPACE: vela-system
     STATUS: deployed
     REVISION: 1
     TEST SUITE: None
     Running cmd: ['helm', 'get', 'manifest', '--namespace', 'vela-system', 'oam-local']
     Running cmd: ['kubectl', 'get', '-oyaml', '-f', '-']
     Objects applied to cluster:
       → pulsar-cluster:componentdefinition
       → postgres:traitdefinition
       → pulsar-namespace:traitdefinition
       → pulsar-topic:traitdefinition

     Step 1 - 0.08s (Force update)
     Step 2 - 1.11s (Deploying)
     DONE IN: 1.19s

Any progress on this?

nothing in the output above did a force uninstall or force delete. what am i missing?

What does this script in Step 1 do?
Running cmd: python3 /Users/christian/.local/share/tilt-dev/tilt_modules/github.com/tilt-dev/tilt-extensions/helm_resource/helm-delete-helper.py
As I already alluded to above, a normal local_resource call with just helm update --install does the trick.

oops, my bad, i misunderstood your message.
yes, clicking the "force update" button will delete the workload before reinstalling. This happens for all workloads, not just helm.
normal deploys (running tilt up, modifying a file) will update the resource in-place. closing this as working as intended

repo: tilt-dev/tilt-extensions


text:
Plugin stopped working

I love the plugin and use it almost daily. Yesterday, I couldn't get it to work at all, and am still having the same issue today. Any ideas of what I can try?
Thanks in advance for any help :)

Thanks for the issue update. Will have a look.

Seems like it could be a compatibility issue with the emoji shortcodes plugin. I disabled that plugin and the reference plugin worked again.

thanks for the update, will mark this as closed for now, I am not sure there is a perfect way to solve the conflicts without changing the bahavior. 😢

repo: tim-hub/obsidian-bible-reference