profile
viewpoint
Uladzimir Havenchyk havenchyk @toptal Minsk, Belarus #TypeScript #JavaScript #React #Node

jamiebuilds/babel-react-optimize 1670

:rocket: A Babel preset and plugins for optimizing React code.

electron-archive/grunt-electron-installer 386

Grunt plugin to build Windows installers for Electron apps

havenchyk/nbrb-currency 1

This repository contains sources of package for getting of currencies of the National Bank of the Republic of Belarus.

havenchyk/angular-webpack-demo 0

Sample app for angular and webpack.

havenchyk/bb-rest-app 0

Backbone sample app

havenchyk/coding-interviews 0

Created with CodeSandbox

havenchyk/commons 0

Simple functions shared among the sinon end user libraries

havenchyk/events-aggregator 0

The aggregator of events in Belarus

havenchyk/favicons 0

Created with CodeSandbox

PullRequestReviewEvent

issue commentcypress-io/cypress

browserslist extends not working with cypress

any reason to use browserify-preprocessor instead of webpack-preprocessor?

marcneander

comment created time in 13 days

issue commentcypress-io/cypress

Cannot run example specs - Webpack Compilation Error

Might be a duplication of https://github.com/cypress-io/cypress/issues/8364

aplaskota

comment created time in 21 days

pull request commenttoptal/simple-react-calendar

chore(deps-dev): bump stylus from 0.54.7 to 0.54.8

@dependabot merge

dependabot-preview[bot]

comment created time in 23 days

PullRequestReviewEvent
PullRequestReviewEvent

pull request commenttoptal/simple-react-calendar

chore(deps-dev): bump @types/jest from 25.2.3 to 26.0.14

@dependabot recreate

dependabot-preview[bot]

comment created time in a month

PullRequestReviewEvent

pull request commenttoptal/simple-react-calendar

chore(deps-dev): bump css-loader from 3.6.0 to 4.3.0

@dependabot merge

dependabot-preview[bot]

comment created time in a month

PullRequestReviewEvent

pull request commenttoptal/simple-react-calendar

chore(deps): [security] bump bl from 1.2.2 to 1.2.3

@dependabot merge

dependabot-preview[bot]

comment created time in a month

PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent

startedcheckly/theheadless.dev

started time in 2 months

pull request commenttoptal/simple-react-calendar

chore(deps-dev): bump jest from 26.1.0 to 26.4.2

@dependabot merge

dependabot-preview[bot]

comment created time in 2 months

PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent

pull request commenttoptal/simple-react-calendar

chore(deps-dev): bump enzyme from 3.10.0 to 3.11.0

@dependabot merge

dependabot-preview[bot]

comment created time in 2 months

delete branch toptal/simple-react-calendar

delete branch : dependabot/npm_and_yarn/markdown-to-jsx-6.11.4

delete time in 2 months

PR closed toptal/simple-react-calendar

chore(deps): bump markdown-to-jsx from 6.11.0 to 6.11.4 dependencies

Bumps markdown-to-jsx from 6.11.0 to 6.11.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/probablyup/markdown-to-jsx/releases">markdown-to-jsx's releases</a>.</em></p> <blockquote> <p>6.11.4: Mitigates security vulnerability where maliciously crafted markdown links could use <code>data:</code> or <code>vbscript:</code> urls to trigger an xss injection ( <a href="https://github-redirect.dependabot.com/probablyup/markdown-to-jsx/issues/306">#306</a> / <a href="https://www.npmjs.com/advisories/1219">https://www.npmjs.com/advisories/1219</a> ), even when using <code>options.disableParsingRawHTML</code></p> <p>Note that currently, the default <code>options.disableParsingRawHTML = false</code> should still only be used for trusted input, as arbitrary html, including script tags.</p> <p>6.11.3 has no changes (I held the publish script upside down; the only change from 6.11.2 is the version number 😅)</p> <h2>6.11.2</h2> <p>[FIX] - Footnote references (<a href="https://github-redirect.dependabot.com/probablyup/markdown-to-jsx/issues/304">#304</a>) thanks <a href="https://github.com/csantos1113">@csantos1113</a></p> <h2>6.11.1</h2> <p>Fix: Support empty style attribute (<a href="https://github-redirect.dependabot.com/probablyup/markdown-to-jsx/issues/296">#296</a>) thanks <a href="https://github.com/cribbles">@cribbles</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/probablyup/markdown-to-jsx/commit/0d2ddc04d2ba9bf4215cc76d6f6e2717db6ddc8e"><code>0d2ddc0</code></a> v6.11.4</li> <li><a href="https://github.com/probablyup/markdown-to-jsx/commit/105d6a6998f9fb23795843355da4a7ed1e106a29"><code>105d6a6</code></a> XSS: Fix sanitizeUrl vbscript/data xss</li> <li><a href="https://github.com/probablyup/markdown-to-jsx/commit/8dfbc86326e7de0557b7c0af32b9483ab21afba4"><code>8dfbc86</code></a> Create CONTRIBUTING.md</li> <li><a href="https://github.com/probablyup/markdown-to-jsx/commit/47f0bb1aa8606e00fc1222eb5450a7b81960358d"><code>47f0bb1</code></a> v6.11.2</li> <li><a href="https://github.com/probablyup/markdown-to-jsx/commit/66e256765c1290002cb43976b50ed93f80dbb429"><code>66e2567</code></a> [FIX] - Footnote references (<a href="https://github-redirect.dependabot.com/probablyup/markdown-to-jsx/issues/304">#304</a>)</li> <li><a href="https://github.com/probablyup/markdown-to-jsx/commit/b653c7a39c84104956dd8b9c84cd74e34d74b334"><code>b653c7a</code></a> v6.11.1</li> <li><a href="https://github.com/probablyup/markdown-to-jsx/commit/9e818504c0cf42f93b71f0b436b7a4a5560ea303"><code>9e81850</code></a> Bump codecov from 3.6.4 to 3.6.5 (<a href="https://github-redirect.dependabot.com/probablyup/markdown-to-jsx/issues/287">#287</a>)</li> <li><a href="https://github.com/probablyup/markdown-to-jsx/commit/bf3ad940399d770443e64a34f146cbad137231f6"><code>bf3ad94</code></a> Bump acorn from 5.7.3 to 5.7.4 (<a href="https://github-redirect.dependabot.com/probablyup/markdown-to-jsx/issues/294">#294</a>)</li> <li><a href="https://github.com/probablyup/markdown-to-jsx/commit/8939f6f5ac4f65a28591480b8f2cedea64d89c28"><code>8939f6f</code></a> Fix: Support empty style attribute (<a href="https://github-redirect.dependabot.com/probablyup/markdown-to-jsx/issues/296">#296</a>)</li> <li><a href="https://github.com/probablyup/markdown-to-jsx/commit/be04c33e6eb4cc7f73df0c292e6e7f4e4659f71d"><code>be04c33</code></a> Update README.md</li> <li>See full diff in <a href="https://github.com/probablyup/markdown-to-jsx/compare/6.11.0...6.11.4">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~ariabuckles">ariabuckles</a>, a new releaser for markdown-to-jsx since your current version.</p> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+1 -9

1 comment

1 changed file

dependabot[bot]

pr closed time in 2 months

PullRequestReviewEvent
PullRequestReviewEvent

delete branch toptal/simple-react-calendar

delete branch : fix-min-date

delete time in 2 months

push eventtoptal/simple-react-calendar

Uladzimir Havenchyk

commit sha 545cada7099eee21c7d281aeacce605c774561ee

fix: change minDate to start at the beginning of the day (#247)

view details

push time in 2 months

PR merged toptal/simple-react-calendar

fix: change minDate to start at the beginning of the day

Description

Fix minDate - it should start at the beginning of the day to cover dates in local timezone.

Previously dates of the month started at 00:00 in local timezone, when minDate was created in local timezone, in UTC+3 it meant that minDate started only at 03:00 -> minDate was after a day that starts at 00:00 -> day can't be selected when it should have been selectable.

Review

  • [x] Verify that all classes affected by the changes have good top-level documentation.
  • [ ] Verify that new code has been covered with specs (and features if applicable).
  • [ ] Verify that a corresponding meaningful changelog entry has been added (* Add Github pull request template), for this change if applicable.
  • [ ] Test manually.
  • [ ] Get two :+1: from code review.

Pre-merge checklist

  • [ ] The PR relates to a single subject with a clear title and description in grammatically correct, complete sentences.
  • [ ] Verify that all new dependencies are included in package.json.
  • [ ] Double check the quality of commit messages.
  • [ ] Squash related commits together.
  • [ ] Verify the branch name starts with NNNN where NNNN is the issue number.

Screenshots

Before After
Insert screenshots and/or screen recordings Insert screenshots and/or screen recordings

Other

Provide additional notes, remarks, links, mention specific people to review,…

+19 -4

2 comments

3 changed files

havenchyk

pr closed time in 2 months

PR opened toptal/simple-react-calendar

fix: change minDate to start at the beginning of the day

NOTE:

This note and all the following italicized text is informational and should be deleted. Additionally, the items non-relevant to the subject of the pull request should be deleted as well. E.g. if task Review checklist items does not apply, or if "Screenshots" can't be provided, the corresponding checklist items ("Screenshots provided…" and "Screen recording…") and their related sections should be removed.

Fill TODO checklist with all the requirements of the ticket. These are the things you will be working on. You should check them as you make progress with the ticket, so other team members and code reviewers know what to look for in the code.

Add WIP label if you're still working on the ticket.

PRs should be merged if and only if all pre-merge requirements are satisfied! Pay special attention to them!

Don't delete the review and pre-merge checklists when filing PRs!!!


Description

Describe the changes and motivations for the pull request, unless obvious from the title.

Review

  • [x] Verify that all classes affected by the changes have good top-level documentation.
  • [ ] Verify that new code has been covered with specs (and features if applicable).
  • [ ] Verify that a corresponding meaningful changelog entry has been added (* Add Github pull request template), for this change if applicable.
  • [ ] Test manually.
  • [ ] Get two :+1: from code review.

Pre-merge checklist

  • [ ] The PR relates to a single subject with a clear title and description in grammatically correct, complete sentences.
  • [ ] Verify that all new dependencies are included in package.json.
  • [ ] Double check the quality of commit messages.
  • [ ] Squash related commits together.
  • [ ] Verify the branch name starts with NNNN where NNNN is the issue number.

Screenshots

Before After
Insert screenshots and/or screen recordings Insert screenshots and/or screen recordings

Other

Provide additional notes, remarks, links, mention specific people to review,…

+19 -4

0 comment

3 changed files

pr created time in 2 months

create barnchtoptal/simple-react-calendar

branch : fix-min-date

created branch time in 2 months

PullRequestReviewEvent

pull request commenttoptal/simple-react-calendar

chore(deps): [security] bump elliptic from 6.5.1 to 6.5.3

@dependabot rebase

dependabot-preview[bot]

comment created time in 2 months

delete branch havenchyk/semantic-release

delete branch : patch-1

delete time in 2 months

PR closed semantic-release/semantic-release

Optimize npm package size

It doesn't make much sense to deliver docs to users via package

+0 -1

3 comments

1 changed file

havenchyk

pr closed time in 2 months

delete branch toptal/simple-react-calendar

delete branch : fix-webpack-merge

delete time in 2 months

push eventtoptal/simple-react-calendar

Uladzimir Havenchyk

commit sha 16ae7b09f5550001f8377a519ee73a3f16f6c206

chore: fix webpack-merge usage (#245)

view details

push time in 2 months

PR merged toptal/simple-react-calendar

chore: fix webpack-merge

NOTE:

This note and all the following italicized text is informational and should be deleted. Additionally, the items non-relevant to the subject of the pull request should be deleted as well. E.g. if task Review checklist items does not apply, or if "Screenshots" can't be provided, the corresponding checklist items ("Screenshots provided…" and "Screen recording…") and their related sections should be removed.

Fill TODO checklist with all the requirements of the ticket. These are the things you will be working on. You should check them as you make progress with the ticket, so other team members and code reviewers know what to look for in the code.

Add WIP label if you're still working on the ticket.

PRs should be merged if and only if all pre-merge requirements are satisfied! Pay special attention to them!

Don't delete the review and pre-merge checklists when filing PRs!!!


Description

Describe the changes and motivations for the pull request, unless obvious from the title.

Review

  • [x] Verify that all classes affected by the changes have good top-level documentation.
  • [ ] Verify that new code has been covered with specs (and features if applicable).
  • [ ] Verify that a corresponding meaningful changelog entry has been added (* Add Github pull request template), for this change if applicable.
  • [ ] Test manually.
  • [ ] Get two :+1: from code review.

Pre-merge checklist

  • [ ] The PR relates to a single subject with a clear title and description in grammatically correct, complete sentences.
  • [ ] Verify that all new dependencies are included in package.json.
  • [ ] Double check the quality of commit messages.
  • [ ] Squash related commits together.
  • [ ] Verify the branch name starts with NNNN where NNNN is the issue number.

Screenshots

Before After
Insert screenshots and/or screen recordings Insert screenshots and/or screen recordings

Other

Provide additional notes, remarks, links, mention specific people to review,…

+4 -4

0 comment

2 changed files

havenchyk

pr closed time in 2 months

PR opened toptal/simple-react-calendar

chore: fix webpack-merge

NOTE:

This note and all the following italicized text is informational and should be deleted. Additionally, the items non-relevant to the subject of the pull request should be deleted as well. E.g. if task Review checklist items does not apply, or if "Screenshots" can't be provided, the corresponding checklist items ("Screenshots provided…" and "Screen recording…") and their related sections should be removed.

Fill TODO checklist with all the requirements of the ticket. These are the things you will be working on. You should check them as you make progress with the ticket, so other team members and code reviewers know what to look for in the code.

Add WIP label if you're still working on the ticket.

PRs should be merged if and only if all pre-merge requirements are satisfied! Pay special attention to them!

Don't delete the review and pre-merge checklists when filing PRs!!!


Description

Describe the changes and motivations for the pull request, unless obvious from the title.

Review

  • [x] Verify that all classes affected by the changes have good top-level documentation.
  • [ ] Verify that new code has been covered with specs (and features if applicable).
  • [ ] Verify that a corresponding meaningful changelog entry has been added (* Add Github pull request template), for this change if applicable.
  • [ ] Test manually.
  • [ ] Get two :+1: from code review.

Pre-merge checklist

  • [ ] The PR relates to a single subject with a clear title and description in grammatically correct, complete sentences.
  • [ ] Verify that all new dependencies are included in package.json.
  • [ ] Double check the quality of commit messages.
  • [ ] Squash related commits together.
  • [ ] Verify the branch name starts with NNNN where NNNN is the issue number.

Screenshots

Before After
Insert screenshots and/or screen recordings Insert screenshots and/or screen recordings

Other

Provide additional notes, remarks, links, mention specific people to review,…

+4 -4

0 comment

2 changed files

pr created time in 2 months

push eventtoptal/simple-react-calendar

Uladzimir Havenchyk

commit sha 783556ebd8ca4125d3bc4dc5189283438d190413

chore: fix webpack-merge

view details

push time in 2 months

create barnchtoptal/simple-react-calendar

branch : fix-webpack-merge

created branch time in 2 months

pull request commenttoptal/simple-react-calendar

chore(deps-dev): bump webpack-merge from 4.2.2 to 5.1.2

@dependabot merge

dependabot-preview[bot]

comment created time in 2 months

PullRequestReviewEvent

pull request commenttoptal/simple-react-calendar

chore(deps-dev): bump @testing-library/react from 10.4.4 to 10.4.9

@dependabot merge @dependabot merge

dependabot-preview[bot]

comment created time in 2 months

PullRequestReviewEvent
more