profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/liginv/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

hamon-in/hamon.in 2

New website of hamon.in

alenthomas/kozhikoden-react-native 1

Android app for Kozhikoden in React Native

GDGKozhikode/gdg_website 1

GDG Kozhikode - Community Website Frontend

liginv/cs-field-guide 1

The Computer Science Field Guide is an online interactive resource/textbook for high school students learning about computer science, developed at the University of Canterbury in New Zealand.

GDGKozhikode/rescuekerala 0

Website for coordinating rehabilitation of people affected in the 2018 Kerala Floods

GDGKozhikode/website 0

GDG Kozhikode Official website

liginv/33-js-concepts 0

📜 33 concepts every JavaScript developer should know.

liginv/A2Z-F16 0

ITP A2Z Course for Fall 2016

liginv/AdventofCode 0

Holiday Special - Coding Practice

issue openedtwbs/bootstrap

Make our bundle SSR friendly

Creating this issue so we don't forget about this.

Idea taken from https://github.com/twbs/bootstrap/pull/33131

created time in 8 minutes

issue closedtwbs/bootstrap

Termux pip install -r requirements.txt

error message that appears in termux: ~/Instagram- $ pip install requirements.txt-contrib-python ERROR: Could not find a version that satisfies the requirement requirements.txt-contrib-python (from versions: none) ERROR: No matching distribution found for requirements.txt-contrib-python ~/Instagram- $ pip install --user requirements.txtERROR: Could not find a version that satisfies the requirement requirements.txt (from versions: none) ERROR: No matching distribution found for requirements.txt ~/Instagram- $ pip list Package Version


appdirs 1.4.4 certifi 2021.5.30 chardet 4.0.0 colorama 0.4.4 distlib 0.3.2 filelock 3.0.12 idna 2.10 pip 21.1.2 pipenv 2021.5.29 psutil 5.8.0 requests 2.25.1 setuptools 56.0.0 six 1.16.0 Slowloris 0.2.3 urllib3 1.26.5 virtualenv 20.4.7 virtualenv-clone 0.5.4

closed time in 16 minutes

XRezendDevil

issue openedtwbs/bootstrap

Termux pip install -r requirements.txt

error message that appears in termux: ~/Instagram- $ pip install requirements.txt-contrib-python ERROR: Could not find a version that satisfies the requirement requirements.txt-contrib-python (from versions: none) ERROR: No matching distribution found for requirements.txt-contrib-python ~/Instagram- $ pip install --user requirements.txtERROR: Could not find a version that satisfies the requirement requirements.txt (from versions: none) ERROR: No matching distribution found for requirements.txt ~/Instagram- $ pip list Package Version


appdirs 1.4.4 certifi 2021.5.30 chardet 4.0.0 colorama 0.4.4 distlib 0.3.2 filelock 3.0.12 idna 2.10 pip 21.1.2 pipenv 2021.5.29 psutil 5.8.0 requests 2.25.1 setuptools 56.0.0 six 1.16.0 Slowloris 0.2.3 urllib3 1.26.5 virtualenv 20.4.7 virtualenv-clone 0.5.4

created time in 23 minutes

create barnchtwbs/bootstrap

branch : pr/33537

created branch time in 43 minutes

issue commenttwbs/bootstrap

BS Jquery plugins become available only after document loaded.

As far as I can tell, the reason for this is data-bs-no-jquery or to be exact, that we check for this data attribute to exist when registering our components with jQuery as this will prevent us from doing so.

See https://github.com/twbs/bootstrap/blob/9485172017868952047da5f188bc13a92ef0435d/js/src/util/index.js#L194-L202

https://github.com/twbs/bootstrap/blob/9485172017868952047da5f188bc13a92ef0435d/js/src/util/index.js#L214-L216

The PR that added this flag https://github.com/twbs/bootstrap/pull/29191

As with the issue Rohit mentioned, if Bootstrap is loaded in the <head> section, document.body isn't defined and thus hasAttribute will throw an error. This has been worked around by defering the registration of jQuery plugins until the DOM is loaded because in that case we can be sure that document.body exists.

rpokrovskij

comment created time in an hour

pull request commenttwbs/bootstrap

Add horizontal collapse support

cough #31681 (comment) Not sure if I should feel ignored.. :P

Lol, nooo, I feel so bad. Sorry for not seeing that! 😅

mdo

comment created time in 2 hours

issue commenttwbs/bootstrap

BS Jquery plugins become available only after document loaded.

@alpadev I still do not understand why boostrap.Tooltip('#myId') is available immediately when $("").tooltip() not ... Till I could understand this I will be very sceptic about my abilities to understand this decision. What about working with UMD with webpack I am ok with current situation, my report there is just a suggestion to "add this to the documentation" (those type of errors are very unobvious and you can save many working hours for our collegues).

rpokrovskij

comment created time in 2 hours

delete branch twbs/bootstrap

delete branch : jo-ssr-friendly

delete time in 2 hours

PR closed twbs/bootstrap

Reviewers
being ssr friendly when accessing dom objects has conflicts js v5

Hi :)

A small PR to allow Bootstrap to be SSR friendly.

I had this idea in mind for quite a long time and it'll avoid developers some headache on how to handle errors like document is undefined or windows is undefined if they use SSR frameworks (for example Gatsby or Next.js)

I added an ESLint plugin to enforce that in all of our source code: https://www.npmjs.com/package/eslint-plugin-ssr-friendly

If you think it's not a relevant do not hesitate to close my PR 👍

+159 -81

17 comments

23 changed files

Johann-S

pr closed time in 2 hours

pull request commenttwbs/bootstrap

being ssr friendly when accessing dom objects

Would be nice to have this but yeah right now it's outdated.

Johann-S

comment created time in 2 hours

pull request commenttwbs/bootstrap

Add horizontal collapse support

cough https://github.com/twbs/bootstrap/pull/31681#issuecomment-808467279 Not sure if I should feel ignored.. :P

mdo

comment created time in 2 hours

issue closedtwbs/bootstrap

dropdown-end causes horizontal scrollbar

Browser: Chrome 87 OS: Ubuntu

Dropdown menus with class "dropdown-end" for alignment to the right are place partly out of the viewport before they are moved to the left with translate(). This leads to a horzontal scrollbar:

Example: https://codepen.io/aimeos/pen/jOVELyo

closed time in 2 hours

aimeos

issue commenttwbs/bootstrap

dropdown-end causes horizontal scrollbar

Thinking we can close this out then. Happy to re-open if there's more we can do.

aimeos

comment created time in 2 hours

push eventtwbs/bootstrap

Matt Dufresne

commit sha 9485172017868952047da5f188bc13a92ef0435d

fix error in javascript example under Asynchronous functions and transitions section

view details

push time in 2 hours

release mui-org/material-ui

v5.0.0-alpha.37

released time in 2 hours

PR merged twbs/bootstrap

Fix error in JavaScript doc example docs v5

Remove the # symbol from the "Asynchronous functions and transitions" JavaScript example since it's uncommon to use # symbols in id attributes.

+1 -1

1 comment

1 changed file

mattdufresne

pr closed time in 2 hours

pull request commenttwbs/bootstrap

Add horizontal collapse support

These lines are what makes .width functional:

https://github.com/twbs/bootstrap/blob/2b2183a96ed7380b3ddb166be54dc25ae362ea9c/js/src/collapse.js#L54

https://github.com/twbs/bootstrap/blob/2b2183a96ed7380b3ddb166be54dc25ae362ea9c/js/src/collapse.js#L268-L270

Switching to any other class would require changing some JS. Arguably no one should be using .width because it's completely undocumented and unsupported, so I'm in favor of changing it, but wanted to raise that it could be a breaking change to someone out there.

mdo

comment created time in 2 hours

PR closed sindresorhus/awesome

Add Django

<!-- Congrats on creating an Awesome list! 🎉 -->

<!-- Please fill in the below placeholders -->

[Insert URL to the list here] https://github.com/UlugbekMuslitdinov/awesome-django#readme

[Explain what this list is about and why it should be included here]: This list contains sources about Django Python Web Framework. Django holds one of the leading positions in the Web Development tools list and it deserves to get the place in your list also.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

  • Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
  • You have to review at least 2 other open pull requests. Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
  • You have read and understood the instructions for creating a list.
  • This pull request has a title in the format Add Name of List.
    • Add Swift
    • Add Software Architecture
    • Update readme.md
    • Add Awesome Swift
    • Add swift
    • add Swift
    • Adding Swift
    • Added Swift
  • Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
    • - [iOS](…) - Mobile operating system for Apple phones and tablets.
    • - [Framer](…) - Prototyping interactive UI designs.
    • - [iOS](…) - Resources and tools for iOS development.
    • - [Framer](…)
    • - [Framer](…) - prototyping interactive UI designs
  • Your entry should be added at the bottom of the appropriate category.
  • The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

  • Has been around for at least 30 days.<br>That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
  • Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
  • Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
  • The default branch should be named main, not master.
  • Includes a succinct description of the project/theme at the top of the readme. (Example)
    • Mobile operating system for Apple phones and tablets.
    • Prototyping interactive UI designs.
    • Resources and tools for iOS development.
    • Awesome Framer packages and tools.
  • It's the result of hard work and the best I could possibly produce. If you have not put in considerable effort into your list, your pull request will be immediately closed.
  • The repo name of your list should be in lowercase slug format: awesome-name-of-list.
    • awesome-swift
    • awesome-web-typography
    • awesome-Swift
    • AwesomeWebTypography
  • The heading title of your list should be in title case format: # Awesome Name of List.
    • # Awesome Swift
    • # Awesome Web Typography
    • # awesome-swift
    • # AwesomeSwift
  • Non-generated Markdown file in a GitHub repo.
  • The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
  • Not a duplicate. Please search for existing submissions.
  • Only has awesome items. Awesome lists are curations of the best, not everything.
  • Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
  • Includes a project logo/illustration whenever possible.
    • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
    • The image should link to the project website or any relevant website.
    • The image should be high-DPI. Set it to maximum half the width of the original image.
  • Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
  • Includes the Awesome badge.
    • Should be placed on the right side of the readme heading.
      • Can be placed centered if the list has a centered graphics header.
    • Should link back to this list.
  • Has a Table of Contents section.
    • Should be named Contents, not Table of Contents.
    • Should be the first section in the list.
    • Should only have one level of nested lists, preferably none.
    • Must not feature Contributing or Footnotes sections.
  • Has an appropriate license.
    • We strongly recommend the CC0 license, but any Creative Commons license will work.
      • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).
    • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
    • Place a file named license or LICENSE in the repo root with the license text.
    • Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
    • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
  • Has contribution guidelines.
    • The file should be named contributing.md. Casing is up to you.
    • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
    • The section should not appear in the Table of Contents.
  • All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
  • Has consistent formatting and proper spelling/grammar.
    • The link and description are separated by a dash. <br>Example: - [AVA](…) - JavaScript test runner.
    • The description starts with an uppercase character and ends with a period.
    • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
  • Doesn't use hard-wrapping.
  • Doesn't include a Travis badge.<br>You can still use Travis for list linting, but the badge has no value in the readme.
  • Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

+1 -0

0 comment

1 changed file

UlugbekMuslitdinov

pr closed time in 3 hours

PR opened sindresorhus/awesome

Added Django Framework

<!-- Congrats on creating an Awesome list! 🎉 -->

<!-- Please fill in the below placeholders -->

[Insert URL to the list here] https://github.com/UlugbekMuslitdinov/awesome-django#readme

[Explain what this list is about and why it should be included here]: This list contains sources about Django Python Web Framework. Django holds one of the leading positions in the Web Development tools list and it deserves to get the place in your list also.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

  • Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
  • You have to review at least 2 other open pull requests. Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
  • You have read and understood the instructions for creating a list.
  • This pull request has a title in the format Add Name of List.
    • Add Swift
    • Add Software Architecture
    • Update readme.md
    • Add Awesome Swift
    • Add swift
    • add Swift
    • Adding Swift
    • Added Swift
  • Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
    • - [iOS](…) - Mobile operating system for Apple phones and tablets.
    • - [Framer](…) - Prototyping interactive UI designs.
    • - [iOS](…) - Resources and tools for iOS development.
    • - [Framer](…)
    • - [Framer](…) - prototyping interactive UI designs
  • Your entry should be added at the bottom of the appropriate category.
  • The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

  • Has been around for at least 30 days.<br>That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
  • Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
  • Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
  • The default branch should be named main, not master.
  • Includes a succinct description of the project/theme at the top of the readme. (Example)
    • Mobile operating system for Apple phones and tablets.
    • Prototyping interactive UI designs.
    • Resources and tools for iOS development.
    • Awesome Framer packages and tools.
  • It's the result of hard work and the best I could possibly produce. If you have not put in considerable effort into your list, your pull request will be immediately closed.
  • The repo name of your list should be in lowercase slug format: awesome-name-of-list.
    • awesome-swift
    • awesome-web-typography
    • awesome-Swift
    • AwesomeWebTypography
  • The heading title of your list should be in title case format: # Awesome Name of List.
    • # Awesome Swift
    • # Awesome Web Typography
    • # awesome-swift
    • # AwesomeSwift
  • Non-generated Markdown file in a GitHub repo.
  • The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
  • Not a duplicate. Please search for existing submissions.
  • Only has awesome items. Awesome lists are curations of the best, not everything.
  • Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
  • Includes a project logo/illustration whenever possible.
    • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
    • The image should link to the project website or any relevant website.
    • The image should be high-DPI. Set it to maximum half the width of the original image.
  • Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
  • Includes the Awesome badge.
    • Should be placed on the right side of the readme heading.
      • Can be placed centered if the list has a centered graphics header.
    • Should link back to this list.
  • Has a Table of Contents section.
    • Should be named Contents, not Table of Contents.
    • Should be the first section in the list.
    • Should only have one level of nested lists, preferably none.
    • Must not feature Contributing or Footnotes sections.
  • Has an appropriate license.
    • We strongly recommend the CC0 license, but any Creative Commons license will work.
      • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).
    • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
    • Place a file named license or LICENSE in the repo root with the license text.
    • Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
    • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
  • Has contribution guidelines.
    • The file should be named contributing.md. Casing is up to you.
    • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
    • The section should not appear in the Table of Contents.
  • All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
  • Has consistent formatting and proper spelling/grammar.
    • The link and description are separated by a dash. <br>Example: - [AVA](…) - JavaScript test runner.
    • The description starts with an uppercase character and ends with a period.
    • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
  • Doesn't use hard-wrapping.
  • Doesn't include a Travis badge.<br>You can still use Travis for list linting, but the badge has no value in the readme.
  • Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

+1 -0

0 comment

1 changed file

pr created time in 3 hours

pull request commenttwbs/bootstrap

Parse JSON data attribute for dropdown

Okay, this behavior still does not fully pass the popper config, since you can not pass the functions in this way 🙂 Configuration without function should work fine IMO.

Ya, not aware of any way to reasonably accomplish that, unless you do strange non-standard things like passing function names for functions available in the global scope. Which seemed bad IMO.

Any feedback on the 4 points in my previous comment?

719media

comment created time in 3 hours

issue commenttwbs/bootstrap

BS Jquery plugins become available only after document loaded.

Arguably there has been some paradigm shift away from jQuery with v5 IMO. While in v4 (and earlier) Bootstrap heavily depended on jQuery this isn't the case with v5 anymore. The only leftovers are the definitions for those jQuery plugins. Thus I'm not sure if creating a separate jquery bundle is really a good approach or supports this idea.

That's also the reason why we don't require or import jQuery because that would make jQuery a dependency again which shouldn't be the case if someone uses Bootstrap without jQuery (by making use of the API introduced in v5).

I'd like to argue that bundlers are a different topic in general. Some of them require additional steps to properly set things up and they may provide extra functionality that depends on the bundler that is used. In webpack for example you may use the ProvidePlugin to have Webpack take care of importing jQuery automatically even when there are no explicit imports. IMO a bundler environment shouldn't make use of an already bundled version, like the UMD bundle, because of tree shaking but thats a different story.

About possible sollutions.

One you figured out by yourself already and I'm not sure what's wrong with this approach. For example, if you was to load bootstrap in the <head> section, most likely you would have to delay the execution anyway because the DOM isn't parsed yet. Event listeners are executed in the order they have been added, so as long you add the DOMContentLoaded listener after including the Bootstrap bundle, you should be fine.

On a side note, in your example there is no need for the IIFE, so this would be enough.

document.addEventListener("DOMContentLoaded", function (event) {
  $('[data-bs-toggle="tooltip"]').tooltip()
});

In general, I'm not sure about the intention behind this data-bs-no-jquery. I can't imagine this is widely used. My assumption about this, as a use case, is that someone uses jQuery but got other plugins loaded that would conflict with the naming of those from Bootstrap and calling noConflict on each conflicting one, is tedious or not possible or something. Or someone is really concerned about the resource usage of the JS code.

We could either remove that flag or move it on the html element instead. That wouldn't require us to postpone the checks for that flag, like with on the body. And as such there would be no need to defer our plugin definitions on to the DOMContentLoaded event. But that's some breaking change so no idea if that's feasible.

In theory we also could remove those jQuery plugin stuff completely from our bundle and add some generic snippet to the documentations. Breaking change again but at least provides some value in terms of bundle size. And the user can decide how and when and if to define those jQuery plugins or not.

rpokrovskij

comment created time in 4 hours

MemberEvent

pull request commentsindresorhus/awesome

Add Privacy

The Contributing.md causes the linter to fail because it's not in the root directory of the repo.

pluja

comment created time in 4 hours

pull request commenttwbs/bootstrap

Add horizontal collapse support

From what I can see, .width isn't in Bootstrap v4 or v5, so why do we need to support a markedly bad class name when it's never been in the codebase? Your other attempt at implementing this was already using .collapse-horizontal, anyways.

mdo

comment created time in 5 hours

MemberEvent

push eventtwbs/bootstrap

dependabot[bot]

commit sha 2b2183a96ed7380b3ddb166be54dc25ae362ea9c

Bump @babel/core from 7.14.5 to 7.14.6 (#34262) Bumps [@babel/core](https://github.com/babel/babel/tree/HEAD/packages/babel-core) from 7.14.5 to 7.14.6. - [Release notes](https://github.com/babel/babel/releases) - [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md) - [Commits](https://github.com/babel/babel/commits/v7.14.6/packages/babel-core) --- updated-dependencies: - dependency-name: "@babel/core" dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: XhmikosR <xhmikosr@gmail.com>

view details

push time in 5 hours

delete branch twbs/bootstrap

delete branch : dependabot/npm_and_yarn/babel/core-7.14.6

delete time in 5 hours

PR merged twbs/bootstrap

Bump @babel/core from 7.14.5 to 7.14.6 dependencies v5

Bumps @babel/core from 7.14.5 to 7.14.6. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/babel/babel/blob/main/CHANGELOG.md"><code>@​babel/core</code>'s changelog</a>.</em></p> <blockquote> <h2>v7.14.6 (2021-06-14)</h2> <h4>:bug: Bug Fix</h4> <ul> <li><code>babel-plugin-transform-spread</code> <ul> <li><a href="https://github-redirect.dependabot.com/babel/babel/pull/13459">#13459</a> babel-plugin-transform-spread add missing argument in build calls (<a href="https://github.com/zxbodya"><code>@​zxbodya</code></a>)</li> <li><a href="https://github-redirect.dependabot.com/babel/babel/pull/13439">#13439</a> Correctly transform spreads of arrays with holes (<a href="https://github.com/nicolo-ribaudo"><code>@​nicolo-ribaudo</code></a>)</li> </ul> </li> <li><code>babel-helpers</code>, <code>babel-plugin-transform-destructuring</code>, <code>babel-plugin-transform-modules-commonjs</code> <ul> <li><a href="https://github-redirect.dependabot.com/babel/babel/pull/13444">#13444</a> fix destructuring of empty string (<a href="https://github.com/lala7573"><code>@​lala7573</code></a>)</li> </ul> </li> <li><code>babel-helper-create-class-features-plugin</code>, <code>babel-plugin-proposal-class-properties</code> <ul> <li><a href="https://github-redirect.dependabot.com/babel/babel/pull/13429">#13429</a> fix: reference to class expression in private method (<a href="https://github.com/lala7573"><code>@​lala7573</code></a>)</li> </ul> </li> <li><code>babel-parser</code> <ul> <li><a href="https://github-redirect.dependabot.com/babel/babel/pull/13428">#13428</a> [ts] Support override modifiers for parameter properties (<a href="https://github.com/sosukesuzuki"><code>@​sosukesuzuki</code></a>)</li> <li><a href="https://github-redirect.dependabot.com/babel/babel/pull/13449">#13449</a> Disallow JSX tag forming after TS non-null assertion (<a href="https://github.com/JLHwung"><code>@​JLHwung</code></a>)</li> </ul> </li> </ul> <h4>:house: Internal</h4> <ul> <li><a href="https://github-redirect.dependabot.com/babel/babel/pull/13423">#13423</a> Faster babel build (<a href="https://github.com/JLHwung"><code>@​JLHwung</code></a>)</li> </ul> <h4>:running_woman: Performance</h4> <ul> <li><code>babel-parser</code> <ul> <li><a href="https://github-redirect.dependabot.com/babel/babel/pull/13453">#13453</a> Faster readRegexp (<a href="https://github.com/JLHwung"><code>@​JLHwung</code></a>)</li> </ul> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/babel/babel/commit/1774e2aaef024f51c84019e2ad7fea2922953947"><code>1774e2a</code></a> v7.14.6</li> <li><a href="https://github.com/babel/babel/commit/ad693cc0a06b98096db3a541b3acb98d756239cd"><code>ad693cc</code></a> Update prettier to 2.3.1 (<a href="https://github.com/babel/babel/tree/HEAD/packages/babel-core/issues/13460">#13460</a>)</li> <li>See full diff in <a href="https://github.com/babel/babel/commits/v7.14.6/packages/babel-core">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

You can trigger a rebase of this PR 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)

</details>

+15 -9

0 comment

2 changed files

dependabot[bot]

pr closed time in 5 hours

push eventtwbs/bootstrap

dependabot[bot]

commit sha a47c055a6f7546caaf2d2310a52607fbf769ff40

Bump postcss from 8.3.3 to 8.3.4 (#34260) Bumps [postcss](https://github.com/postcss/postcss) from 8.3.3 to 8.3.4. - [Release notes](https://github.com/postcss/postcss/releases) - [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md) - [Commits](https://github.com/postcss/postcss/compare/8.3.3...8.3.4) --- updated-dependencies: - dependency-name: postcss dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

XhmikosR

commit sha 1ff0e3524ebe1a5fc26917c33585abae61406865

Merge branch 'main' into dependabot/npm_and_yarn/babel/core-7.14.6

view details

push time in 6 hours

push eventtwbs/bootstrap

dependabot[bot]

commit sha a47c055a6f7546caaf2d2310a52607fbf769ff40

Bump postcss from 8.3.3 to 8.3.4 (#34260) Bumps [postcss](https://github.com/postcss/postcss) from 8.3.3 to 8.3.4. - [Release notes](https://github.com/postcss/postcss/releases) - [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md) - [Commits](https://github.com/postcss/postcss/compare/8.3.3...8.3.4) --- updated-dependencies: - dependency-name: postcss dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

push time in 6 hours