profile
viewpoint
Phan An phanan @InterNations Munich https://phanan.net Author, developer, sleepwalker.

phanan/htaccess 11232

✂A collection of useful .htaccess snippets.

phanan/koel 11107

🐦 A personal music streaming server that works.

lstrojny/functional-php 1612

Primitives for functional programming in PHP

phanan/kupo 360

✅ Simple site launch checklist checker/validator.

koel/app 293

🖥 The desktop application for Koel.

phanan/vue-facebook-signin-button 120

A simple plugin to include a custom Facebook sign-in button into your web app.

phanan/tieqviet 70

A trivial module to convert Vietnamese into the new, experimental, IPA

koel/core 60

The core components and assets of Koel

phanan/cascading-config 55

Bringing the cascading configuration system back to Laravel 5 and its sister project, Lumen.

phanan/slider-puzzle 37

A simple slider puzzle built with Vue

pull request commentvuejs/vuejs.org

Improve methods in inline handlers example

Thanks, but I don't think this change is necessary :)

renjithspace

comment created time in a day

pull request commentvuejs/vuejs.org

[Doc EN]: `transition.md`, example 4, add a forgotten instruction

Thanks!

Haeresis

comment created time in a day

push eventvuejs/vuejs.org

Bruno J. S. Lesieur

commit sha 431fba9434cf1321636c897c3bcd19b8beb001de

[Doc EN]: `transition.md`, example 4, add a forgotten instructi… (#2500) * Indent fix (Biggest update ever) Signed-off-by: Bruno J. S. Lesieur <bruno.lesieur@gmail.com> * Some line return for consistency Signed-off-by: MachinisteWeb <bruno.lesieur@gmail.com> * Align transitions.md example 4 text example with live example Signed-off-by: MachinisteWeb <bruno.lesieur@gmail.com>

view details

push time in a day

PR merged vuejs/vuejs.org

[Doc EN]: `transition.md`, example 4, add a forgotten instruction

Hi @sarahdayan and @chrisvfritz,

Just a small change about the transition file: one instruction in live example is not present in text example associate :)

The line 526 (before)-527 (after) was copy/past to line 482 (just deploy twice (maybe third) the code below my change from tab « Files changed » to see the line I have added).

It is now resolved!

+1 -0

0 comment

1 changed file

Haeresis

pr closed time in a day

startedchrisvfritz/prerender-spa-plugin

started time in a day

pull request commentvuejs/vuejs.org

fix: deduplicate change detection caveat sections

Thanks @sarahdayan!

sarahdayan

comment created time in 2 days

issue closedvuejs/vuejs.org

Repeated reactivity explanations

I noticed that both Reactivity in Depth (section Change Detection Caveats) and List Rendering (section Object Change Detection Caveats) mention the caveats of creating object properties and reactivity. They use slightly different, but fundamentally the same examples.

While this is certainly an important thing to mention, its repetition on both of those pages strikes me as odd and slightly confusing as a user coming back to the guides. I had a brief moment of uncertainty when I realized that it felt as though I've already read that section.

I'm not sure if this is significant enough to be worth correcting. Personally I feel like linking to the Reactivity in Depth page would be an easier to maintain and less confusing solution, though the importance of this explanation, as well as the name of the Reactivity in Depth guide in the section Internals suggesting it's an advanced topic and it's low position on the sidebar menu make me slightly hesitant to change it.

Thoughts?

closed time in 2 days

opl-

push eventvuejs/vuejs.org

Sarah Dayan

commit sha 17ab220c80c6b8cd08fabf65d6c726ef2da0c54b

fix: deduplicate change detection caveat sections (#2497) * fix: deduplicate change detection caveat sections * fix: apply suggestions from review

view details

push time in 2 days

PR merged vuejs/vuejs.org

fix: deduplicate change detection caveat sections

This deduplicates the object change detection caveats sub-section that was on the Reactivity in Depth and List Rendering sections.

For consistency, it also moved the array change detection caveats sub-section from List Rendering sections to Reactivity in Depth, so all caveats are in a single place.

fixes #2352

+47 -99

1 comment

2 changed files

sarahdayan

pr closed time in 2 days

Pull request review commentvuejs/vuejs.org

fix: deduplicate change detection caveat sections

 Every component instance has a corresponding **watcher** instance, which records  ## Change Detection Caveats -Due to the limitations of modern JavaScript (and the abandonment of `Object.observe`), Vue **cannot detect property addition or deletion**. Since Vue performs the getter/setter conversion process during instance initialization, a property must be present in the `data` object in order for Vue to convert it and make it reactive. For example:+Due to limitations in JavaScript, there are types of changes that Vue **cannot detect**. However, there are ways to circumvent them to preserve reactivity.++### With Objects++Vue **cannot detect property addition or deletion**. Since Vue performs the getter/setter conversion process during instance initialization, a property must be present in the `data` object in order for Vue to convert it and make it reactive. For example:

Since we have emphasized that Vue **cannot** in the leading paragraph (L23), emphasizing it again (L27) and again (L62) sounds pretty dramatic IMHO 😅.

sarahdayan

comment created time in 2 days

Pull request review commentvuejs/vuejs.org

fix: deduplicate change detection caveat sections

 Every component instance has a corresponding **watcher** instance, which records  ## Change Detection Caveats -Due to the limitations of modern JavaScript (and the abandonment of `Object.observe`), Vue **cannot detect property addition or deletion**. Since Vue performs the getter/setter conversion process during instance initialization, a property must be present in the `data` object in order for Vue to convert it and make it reactive. For example:+Due to limitations in JavaScript, there are types of changes that Vue **cannot detect**. However, there are ways to circumvent them to preserve reactivity.++### With Objects

Is it "Change detection caveats for objects" or "with objects"? Not a native speaker myself, so…

sarahdayan

comment created time in 2 days

issue closedphanan/koel

Koel lets you log in with the same user multiple times

Koel lets you log in with the same user multiple times. I can login using the same credential many times on different browsers at the same time. This breaks the user security and could lead to potential issues if credentials are intercepted.

closed time in 3 days

Bk8

issue commentphanan/koel

Koel lets you log in with the same user multiple times

This breaks the user security and could lead to potential issues if credentials are intercepted.

I don't think so. A lot of other services (Google/Gmail/Facebook/Twitter included) allows this. Granted, they have a screen to manage the logins and allow you to log out individually, but I don't have any plan to support that.

Bk8

comment created time in 3 days

issue commentvuejs/vuejs.org

Allow cross origin access error

Please use our forum or Discord for questions like this. Thanks.

Ask149

comment created time in 3 days

issue closedvuejs/vuejs.org

Allow cross origin access error

Hi, I'm am working on integrating a vuejs template in spring boot admin, and I was successful in integrating the same. As per the project requirement, I was required to make a GET request to a specific URL which is in the same service ( http://localhost:8080/... ). However, the url of the service varies as per the environment it is running on. But, when the GET call is requested through axios along with the headers for CORS ( Allow Cross Origin... ), I'm getting an error specifying Allow cross origin headers not present. To make sure I try every other alternatives, I've even added the required Bean in Spring Java Code for CorsConfiguration and also added properties for CORS in application.properties file. Could you help me with this issue?

closed time in 3 days

Ask149

pull request commentvuejs/vuejs.org

feat: add rule on arrow functions in option values

Also IMHO, using (or not) arrow function isn't a matter of style, and thus doesn't belong in the Style guide.

sarahdayan

comment created time in 3 days

pull request commentvuejs/vuejs.org

feat: add rule on arrow functions in option values

I wasn't a part of the original discussion, so I guess I'll add my 2¢ here: I see this rule as a "yes and no."

Personally, I now almost always consciously use arrow functions if my methods (as in methods option and lifecycle hooks) don't need to access the Vue instance. If we see this as a variable (because it is), albeit implicit, having it in a function that doesn't make use of it sounds pretty superfluous to me. This also more or less follows the "Principle of Least knowledge," the way I see it.

While arrow functions may be a pitfall for beginners due to them not having a lexical this, I'd argue that it's actually good to fall for it, because it'll make them investigate and better understand the problem.

sarahdayan

comment created time in 3 days

startedtauri-apps/tauri

started time in 3 days

push eventphanan/koel

Phan An

commit sha 8d2b7b3842d655724cd9675756c55abb6216f6dc

fix: tymon/jwt-auth incompatibility with Laravel 5.8

view details

push time in 4 days

push eventkoel/core

Phan An

commit sha fe2e8a24bb991a68c8b64393d15a0e663cf86eb4

feat: context menu for footer

view details

Phan An

commit sha ed06031d3f6577899c9f036786c7481bf2050a5f

fix: hot key didn't work on range inputs

view details

push time in 4 days

startedhasura/graphql-engine

started time in 4 days

push eventphanan/koel

dependabot-preview[bot]

commit sha 9e5843fe66fd0180ccb06328638fcba2115cc046

chore(deps): bump fideloper/proxy from 4.2.2 to 4.3.0 (#1184) Bumps [fideloper/proxy](https://github.com/fideloper/TrustedProxy) from 4.2.2 to 4.3.0. - [Release notes](https://github.com/fideloper/TrustedProxy/releases) - [Commits](https://github.com/fideloper/TrustedProxy/compare/4.2.2...4.3.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

push time in 4 days

PR merged phanan/koel

chore(deps): bump fideloper/proxy from 4.2.2 to 4.3.0 dependencies

Bumps fideloper/proxy from 4.2.2 to 4.3.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/fideloper/TrustedProxy/releases">fideloper/proxy's releases</a>.</em></p> <blockquote> <h2>Support Laravel 8</h2> <p>Laravel 8 uses the newer Symfony 5, but it seems like they haven't changed Trusted Proxy support in this major release.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/fideloper/TrustedProxy/commit/ec38ad69ee378a1eec04fb0e417a97cfaf7ed11a"><code>ec38ad6</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/fideloper/TrustedProxy/issues/133">#133</a> from GrahamCampbell/patch-1</li> <li><a href="https://github.com/fideloper/TrustedProxy/commit/305d1b755864de4a7e96a86742e1f018f06998e4"><code>305d1b7</code></a> Allow Laravel 8</li> <li>See full diff in <a href="https://github.com/fideloper/TrustedProxy/compare/4.2.2...4.3.0">compare view</a></li> </ul> </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
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+7 -7

0 comment

1 changed file

dependabot-preview[bot]

pr closed time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 Also see [Production Deployment Tips](deployment.html).  ### CSP environments -Some environments, such as Google Chrome Apps, enforce Content Security Policy (CSP), which prohibits the use of `new Function()` for evaluating expressions. The full build depends on this feature to compile templates, so is unusable in these environments.+Some environments, such as Google Chrome Apps, enforce Content Security Policy (<abbr title="Content Security Policy">CSP</abbr>), which prohibits the use of `new Function()` for evaluating expressions. The full build depends on this feature to compile templates, so is unusable in these environments.  On the other hand, the runtime-only build is fully CSP-compliant. When using the runtime-only build with [Webpack + vue-loader](https://github.com/vuejs-templates/webpack-simple) or [Browserify + vueify](https://github.com/vuejs-templates/browserify-simple), your templates will be precompiled into `render` functions which work perfectly in CSP environments.  ## Dev Build -**Important**: the built files in GitHub's `/dist` folder are only checked-in during releases. To use Vue from the latest source code on GitHub, you will have to build it yourself!+**Important**: The built files in GitHub's `/dist` folder are only checked-in during releases. To use Vue from the _very latest_ source code on GitHub, you will have to build it yourself!

The emphasis here is unnecessary IMHO.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 The tree of DOM nodes for the HTML above looks like this:  ![DOM Tree Visualization](/images/dom-tree.png) -Every element is a node. Every piece of text is a node. Even comments are nodes! A node is just a piece of the page. And as in a family tree, each node can have children (i.e. each piece can contain other pieces).+Every element is a node. Every piece of text is a node. Even comments are nodes! A node is just a piece of the page. And as in a family tree, each node can have children. (That is, each piece can contain other pieces.) -Updating all these nodes efficiently can be difficult, but thankfully, you never have to do it manually. Instead, you tell Vue what HTML you want on the page, in a template:+Updating all these nodes efficiently can be difficult. But thankfully, you never have to do it manually! Instead, you simply tell Vue the desired HTML in a template:

Please avoid using words like "simply" and "just."

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 Now when we use the `<todo-list>` component, we can optionally define an alterna  However, even this barely scratches the surface of what scoped slots are capable of. For real-life, powerful examples of scoped slot usage, we recommend browsing libraries such as [Vue Virtual Scroller](https://github.com/Akryum/vue-virtual-scroller), [Vue Promised](https://github.com/posva/vue-promised), and [Portal Vue](https://github.com/LinusBorg/portal-vue). -## Deprecated Syntax+## Deprecated Syntax (`slot`)

Not only this is unnecessary (IMHO), it would also change the anchor name and possibly break linking.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 methods: { } ``` -Instead of a computed property, we can define the same function as a method. For the end result, the two approaches are indeed exactly the same. However, the difference is that **computed properties are cached based on their reactive dependencies.** A computed property will only re-evaluate when some of its reactive dependencies have changed. This means as long as `message` has not changed, multiple access to the `reversedMessage` computed property will immediately return the previously computed result without having to run the function again.+Instead of a computed property, you can define the same function as a method. In terms of the end result, the two approaches are indeed exactly the same.++However, the difference is that **computed properties are cached based on their reactive dependencies.** A computed property will only re-evaluate when some of its reactive dependencies have changed. This means as long as `message` has not changed, multiple access to the `reversedMessage` computed property will immediately return the previously computed result without needing to run the function again.

Ditto.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 new Vue({ </script> {% endraw %} -Note that the `<label>` elements are still efficiently re-used, because they don't have `key` attributes.+<p class="tip">

Ditto re: p.tip element.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 order: 303  ## Basics -Vue recommends using templates to build your HTML in the vast majority of cases. There are situations however, where you really need the full programmatic power of JavaScript. That's where you can use the **render function**, a closer-to-the-compiler alternative to templates.+Vue recommends using templates to build your HTML in the vast majority of cases. There are situations however, where you really need the full programmatic power of JavaScript. That's where you can use the **`render()` function**, a closer-to-the-compiler alternative to templates.

"Render function" is the right choice of words here, because, well, it's the name of the (type of this) function.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 For example: <div v-on:click.ctrl="doSomething">Do something</div> ``` -<p class="tip">Note that modifier keys are different from regular keys and when used with `keyup` events, they have to be pressed when the event is emitted. In other words, `keyup.ctrl` will only trigger if you release a key while holding down `ctrl`. It won't trigger if you release the `ctrl` key alone. If you do want such behaviour, use the `keyCode` for `ctrl` instead: `keyup.17`.</p>+<p class="tip">Note that modifier keys are different from regular keys and when used with `keyup` events, they have to be pressed when the event is emitted. In other words, `keyup.ctrl` will only trigger if you release a key while holding down <kbd>ctrl</kbd>. It won't trigger if you release the <kbd>ctrl</kbd> key alone. If you do want such behaviour, use the `keyCode` for <kbd>ctrl</kbd> instead: `keyup.17`.</p>

We might take this chance to remove the p.tip element as well.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 computed: { } ``` -In situations where computed properties are not feasible (e.g. inside nested `v-for` loops), you can use a method:+In situations where `computed` properties are not feasible (e.g., within nested `v-for` loops), you can use a method:

I believe the right word here is "inside" :)

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 new Vue({ }) ``` -Vue templates are compiled into JavaScript, and expressions inside templates will be executed as part of the rendering process. Although the expressions are evaluated against a specific rendering context, due to the complexity of potential global execution environments, it is impractical for a framework like Vue to completely shield you from potential malicious code execution without incurring unrealistic performance overhead. The most straightforward way to avoid this category of problems altogether is to make sure the contents of your Vue templates are always trusted and entirely controlled by you.+Vue templates are compiled into JavaScript, and expressions inside templates are executed as part of the rendering process. Although the expressions are evaluated against a specific rendering context, due to the complexity of potential global execution environments, it is impractical for a framework like Vue to completely shield you from potential malicious code execution without incurring unrealistic performance overhead. The most straightforward way to avoid this category of problems altogether is to make sure the contents of your Vue templates are always trusted and entirely controlled by you.  ## What Vue Does to Protect You  ### HTML content -Whether using templates or render functions, content is automatically escaped. That means in this template:+Whether using templates or render functions, content is automatically escaped.++Consider the following template:  ```html <h1>{{ userProvidedString }}</h1> ``` -if `userProvidedString` contained:+If the value of `userProvidedString` was this:  ```js '<script>alert("hi")</script>' ``` -then it would be escaped to the following HTML:+Then it would be escaped to the following HTML:  ```html &lt;script&gt;alert(&quot;hi&quot;)&lt;/script&gt; ``` -thus preventing the script injection. This escaping is done using native browser APIs, like `textContent`, so a vulnerability can only exist if the browser itself is vulnerable.+Thus preventing the script injection.++This escaping is done using native browser APIs (like `textContent`), so a vulnerability can only exist if the browser itself is vulnerable.

This whole rewritten section, including the change of cases, would break the continuity of the text.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 In the [`dist/` directory of the NPM package](https://cdn.jsdelivr.net/npm/vue/d  - **Compiler**: code that is responsible for compiling template strings into JavaScript render functions. -- **Runtime**: code that is responsible for creating Vue instances, rendering and patching virtual DOM, etc. Basically everything minus the compiler.+- **Runtime**: code that is responsible for creating Vue instances, rendering and patching virtual DOM, etc. ...Basically, everything except the compiler.

I don't think the usage of the ellipsis (or, actually, three dots) here is correct.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 order: 8  ## Mapping an Array to Elements with `v-for` -We can use the `v-for` directive to render a list of items based on an array. The `v-for` directive requires a special syntax in the form of `item in items`, where `items` is the source data array and `item` is an **alias** for the array element being iterated on:+You can use the `v-for` directive to render a list of items based on an array. The `v-for` directive requires a special syntax in the form of <code><var>item</var> in <var>items</var></code>, where <code><var>items</var></code> is the source data array and <code><var>item</var></code> is an **alias** for the current array element of the iteration:

What's happening here?

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 rollup({  When using in-DOM templates or in-JavaScript template strings, the template-to-render-function compilation is performed on the fly. This is usually fast enough in most cases, but is best avoided if your application is performance-sensitive. -The easiest way to pre-compile templates is using [Single-File Components](single-file-components.html) - the associated build setups automatically performs pre-compilation for you, so the built code contains the already compiled render functions instead of raw template strings.+The easiest way to pre-compile templates is using **[Single-File Components](single-file-components.html)**. The associated build setups automatically performs pre-compilation for you, so the built code contains the already compiled render functions instead of raw template strings. -If you are using Webpack, and prefer separating JavaScript and template files, you can use [vue-template-loader](https://github.com/ktsn/vue-template-loader), which also transforms the template files into JavaScript render functions during the build step.+If you are using Webpack, and prefer separate JavaScript and template files, you can use [vue-template-loader](https://github.com/ktsn/vue-template-loader), which also transforms the template files into JavaScript render functions during the build step.

"Separating" actually is the right word here.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 var watchExampleVM = new Vue({ </script> {% endraw %} -In this case, using the `watch` option allows us to perform an asynchronous operation (accessing an API), limit how often we perform that operation, and set intermediary states until we get a final answer. None of that would be possible with a computed property.+In this case, using the `watch` option allows you to:

Here, rewriting the paragraph into a list doesn't make it much clearer (if at all) when actually loses the existing fluency.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 var vm = new Vue({ }) ``` -Although not strictly associated with the [MVVM pattern](https://en.wikipedia.org/wiki/Model_View_ViewModel), Vue's design was partly inspired by it. As a convention, we often use the variable `vm` (short for ViewModel) to refer to our Vue instance.+Although not strictly associated with the [<abbr title="Model View ViewModel">MVVM</abbr> pattern](https://en.wikipedia.org/wiki/Model_View_ViewModel), Vue's design was partly inspired by it. As a convention, we often use the variable `vm` (short for _ViewModel_) to refer to our Vue instance.  When you create a Vue instance, you pass in an **options object**. The majority of this guide describes how you can use these options to create your desired behavior. For reference, you can also browse the full list of options in the [API reference](../api/#Options-Data). -A Vue application consists of a **root Vue instance** created with `new Vue`, optionally organized into a tree of nested, reusable components. For example, a todo app's component tree might look like this:+A Vue application consists of a **root Vue instance** created with `new Vue`, optionally organized into a tree of nested, reusable components.++For example, a todo app's component tree might look like this:

This reads better as one paragraph IMHO.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 You can use the following modifiers to trigger mouse or keyboard event listeners - `.shift` - `.meta` -> Note: On Macintosh keyboards, meta is the command key (⌘). On Windows keyboards, meta is the Windows key (⊞). On Sun Microsystems keyboards, meta is marked as a solid diamond (◆). On certain keyboards, specifically MIT and Lisp machine keyboards and successors, such as the Knight keyboard, space-cadet keyboard, meta is labeled “META”. On Symbolics keyboards, meta is labeled “META” or “Meta”.+<p class="tip">**Note:**

Ditto re: p.tip elements.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 Either way, the rendered HTML will be: </div> ``` -Note that **`v-slot` can only be added to a `<template>`** (with [one exception](#Abbreviated-Syntax-for-Lone-Default-Slots)), unlike the deprecated [`slot` attribute](#Deprecated-Syntax).+<p class="tip">Note that <code>v-slot</code> can only be added to a <code>&lt;template&gt;</code> (with <a href="#Abbreviated-Syntax-for-Lone-Default-Slots">one exception</a>), unlike the deprecated <a href="#Deprecated-Syntax"><code>slot</code> attribute</a>).</p>

We tend to avoid these p.tip now actually and instead try to blend "tips" into actual content.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 var vm = new Vue({ </script> {% endraw %} -Here we have declared a computed property `reversedMessage`. The function we provided will be used as the getter function for the property `vm.reversedMessage`:+Here the computed property `reversedMessage` is declared. The function we provided will be used as the getter function for the property `vm.reversedMessage`:

Shouldn't passive voice be avoided?

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 new Vue({ }) ``` -This would pin the element 200px from the top of the page. But what happens if we run into a scenario when we need to pin the element from the left, instead of the top? Here's where a dynamic argument that can be updated per component instance comes in very handy:+This would pin the element `200px` from the top of the page. But what happens if you run into a scenario when you need to pin the element from the left, instead of the top?

An arguably better alternative is to replace "200px" with "200 pixels" as it's what we want to convey here.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 computed: {  In comparison, a method invocation will **always** run the function whenever a re-render happens. -Why do we need caching? Imagine we have an expensive computed property **A**, which requires looping through a huge Array and doing a lot of computations. Then we may have other computed properties that in turn depend on **A**. Without caching, we would be executing **A**’s getter many more times than necessary! In cases where you do not want caching, use a method instead.+#### Why do we need caching?++Imagine you have an expensive computed property **A**, which requires looping through a huge Array and doing a lot of computations. Then you may have other computed properties that, in turn, depend on **A**. Without caching, you would be executing **A**’s getter many more times than necessary!++In cases where you do not want caching, use a method instead.  ### Computed vs Watched Property -Vue does provide a more generic way to observe and react to data changes on a Vue instance: **watch properties**. When you have some data that needs to change based on some other data, it is tempting to overuse `watch` - especially if you are coming from an AngularJS background. However, it is often a better idea to use a computed property rather than an imperative `watch` callback. Consider this example:+Vue does provide a more generic way to observe and react to data changes on a Vue instance: **watch properties**.++When you have some data that needs to change based on some other data, it is tempting to overuse `watch` (especially if you are coming from an AngularJS background).++However, it is often a better idea to use a computed property rather than an imperative `watch` callback. Consider this example:

Ditto. This whole section as one paragraph reads better than the split-up version to me.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 var vm = new Vue({ </script> {% endraw %} -Here we have declared a computed property `reversedMessage`. The function we provided will be used as the getter function for the property `vm.reversedMessage`:+Here the computed property `reversedMessage` is declared. The function we provided will be used as the getter function for the property `vm.reversedMessage`:  ``` js console.log(vm.reversedMessage) // => 'olleH' vm.message = 'Goodbye' console.log(vm.reversedMessage) // => 'eybdooG' ``` -You can open the console and play with the example vm yourself. The value of `vm.reversedMessage` is always dependent on the value of `vm.message`.+You can open the console and play with the example `vm` yourself. The value of `vm.reversedMessage` is always dependent on the value of `vm.message`. -You can data-bind to computed properties in templates just like a normal property. Vue is aware that `vm.reversedMessage` depends on `vm.message`, so it will update any bindings that depend on `vm.reversedMessage` when `vm.message` changes. And the best part is that we've created this dependency relationship declaratively: the computed getter function has no side effects, which makes it easier to test and understand.+You can data-bind to computed properties in templates just like a normal property. Vue is aware that `vm.reversedMessage` depends on `vm.message`, so it will update any bindings that depend on `vm.reversedMessage` when `vm.message` changes.++And the best part is that this dependency relationship is created _declaratively_. The computed getter function has no side effects, which makes it easier to test and understand.

Splitting the paragraph into two this way actually hurts continuity IMHO.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 That means the value of `v-slot` can actually accept any valid JavaScript expres </current-user> ``` -This can make the template much cleaner, especially when the slot provides many props. It also opens other possibilities, such as renaming props, e.g. `user` to `person`:+This can make the template much cleaner, especially when the slot provides many props. It also opens other possibilities, such as renaming props (like renaming `user` to `person`):  ``` html <current-user v-slot="{ user: person }">   {{ person.firstName }} </current-user> ``` -You can even define fallbacks, to be used in case a slot prop is undefined:+You can even define fallbacks, to be used in case a slot prop is `undefined`:

Here we want to talk about the status of a slot prop (undefined) and not its actual value (undefined), so the existing usage is more correct.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 That means the value of `v-slot` can actually accept any valid JavaScript expres </current-user> ``` -This can make the template much cleaner, especially when the slot provides many props. It also opens other possibilities, such as renaming props, e.g. `user` to `person`:+This can make the template much cleaner, especially when the slot provides many props. It also opens other possibilities, such as renaming props (like renaming `user` to `person`):

I'd prefer the existing version, which doesn't have the duplication of renaming and the unnecessary usage of parentheses.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 You can even define fallbacks, to be used in case a slot prop is undefined:  > New in 2.6.0+ -Similar to `v-on` and `v-bind`, `v-slot` also has a shorthand, replacing everything before the argument (`v-slot:`) with the special symbol `#`. For example, `v-slot:header` can be rewritten as `#header`:+Similar to `v-on` and `v-bind`, `v-slot` also has a shorthand, replacing everything before the argument (`v-slot:`) with the special symbol `#`.

IMHO the current one-paragraph approach sounds better in terms of continuity.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 So, committing to this architectural approach most of the time implies developin  ### Effects of DevOps -The adoption of [DevOps](https://martinfowler.com/bliki/DevOpsCulture.html) culture, tools and agile engineering practices has, among other things, the nice effect of increasing the collaboration between the roles of development and operations. One of the main problem of the past (but also today in some realities) is that the dev team tended to be uninterested in the operation and maintenance of a system once it was handed over to the ops team, while the latter tended to be not really aware of the system's business goals and, therefore, reluctant in satisfying the operational needs of the system (also referred to as "whims of developers").+The adoption of [DevOps](https://martinfowler.com/bliki/DevOpsCulture.html) culture, tools and agile engineering practices has, among other things, the nice effect of increasing the collaboration between the roles of development and operations. One of the main problem of the past (but also today in some places) is that the dev team tended to be uninterested in the operation and maintenance of a system once they handed it over to the ops team&mdash;while the latter tended to be not really aware of the system's business goals, and were therefore reluctant in satisfying the operational needs of the system (also referred to as "whims of developers").

Can we replace &mdash; with the Unicode character "—" itself?

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 It might be tempting to create a very complex solution based on the example, but ## Wrapping Up That's it. With all those bits and pieces created we can now re-use the `GoogleMapLoader` component as a base for all our maps by passing different templates to each one of them. Imagine that you need to create another map with different Markers or just Markers without Polylines. By using the above pattern it becomes very easy as we just need to pass different content to the `GoogleMapLoader` component. -This pattern is not strictly connected to Google Maps; it can be used with any library to set the base component and expose the library's API that might be then used in the component that summoned the base component.\ No newline at end of file+This pattern is not strictly connected to Google Maps. It can be used with any library to set the base component and expose the library's API that might be then used in the component that summoned the base component.

Here I think a semicolon works better.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 There are usually two cases where it's tempting to mutate a prop:   }   ``` -2. **The prop is passed in as a raw value that needs to be transformed.** In this case, it's best to define a computed property using the prop's value:+2. **The prop is passed in as a raw value that needs to be transformed.** In this case, it's best to define a `computed` property using the prop's value:

When it's not necessary to revert this change, "computed property" is more or less how we refer to it and should be used just fine as-is.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 This can be useful sometimes, but it's not a good idea when you're trying to lis </label> ``` -In that case, the `.native` listener in the parent would silently break. There would be no errors, but the `onFocus` handler wouldn't be called when we expected it to.+In that case, the `.native` listener in the parent would silently break. There would be no errors, but the `onFocus` handler wouldn't be called when you expect.

Here as well. Basically I'd prefer "we" over "you" whenever applicable.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 When you wrap a component with `keep-alive`, its state will be preserved and the ``` This technique can be useful to improve user experience. For example, imagine a user starts entering comments into a text input and then decides to navigate away. If the user then navigated back, their comments would still be preserved. -Once you use keep-alive, then you have access to two more lifecycle hooks: `activated` and `deactivated`. If you do want to clean up or change data when a keep-alive component is removed, you can do so in the `deactivated` hook.+Once you use `<keep-alive>`, then you have access to two more lifecycle hooks: `activated` and `deactivated`. If you do want to clean up or change data when a `<keep-alive>` component is removed, you can do so in the `deactivated` hook.

If you do want to clean up or change data when a <keep-alive> component is removed, you can do so in the deactivated hook.

Here <keep-alive> shouldn't be a tag, as we're talking about the wrapped component, not <keep-alive> itself.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 order: 13  So you built your first Vue.js app using the amazing [Vue.js webpack template](https://github.com/vuejs-templates/webpack) and now you really want to show off with your colleagues by demonstrating that you can also run it in a Docker container. -Let's start by creating a `Dockerfile` in the root folder of our project:+Let's begin by creating a `Dockerfile` in the root folder of your project:

I'd prefer keeping the first-person view here, as it's more friendly this way.

Zearin

comment created time in 4 days

Pull request review commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

 EXPOSE 8080 CMD [ "http-server", "dist" ] ``` -It may seem redundant to first copy `package.json` and `package-lock.json` and then all project files and folders in two separate steps but there is actually [a very good reason for that](http://bitjudo.com/blog/2014/03/13/building-efficient-dockerfiles-node-dot-js/) (spoiler: it allows us to take advantage of cached Docker layers).+It may seem redundant to first copy `package.json` and `package-lock.json` and then all project files and folders in two separate steps but there is actually [a very good reason for that](http://bitjudo.com/blog/2014/03/13/building-efficient-dockerfiles-node-dot-js/). (Spoiler: it allows you to take advantage of cached Docker layers.) -Now let's build the Docker image of our Vue.js app:+Now let's build the Docker image of your Vue.js app:  ```bash docker build -t vuejs-cookbook/dockerize-vuejs-app . ``` -Finally, let's run our Vue.js app in a Docker container:+Finally, let's run your Vue.js app in a Docker container:  ```bash docker run -it -p 8080:8080 --rm --name dockerize-vuejs-app-1 vuejs-cookbook/dockerize-vuejs-app ``` -We should be able to access our Vue.js app on `localhost:8080`.+You should be able to access your Vue.js app on `localhost:8080`.  ## Real-World Example -In the previous example, we used a simple, zero-configuration command-line [http server](https://github.com/indexzero/http-server) to serve our Vue.js app which is perfectly ok for quick prototyping and _may_ even be ok for simple production scenarios. After all, the documentation says:+In the previous example, we used a simple, zero-configuration command-line [http server](https://github.com/indexzero/http-server) to serve our Vue.js app which is perfectly okay for quick prototyping and _may_ even be ok for simple production scenarios. After all, the documentation says:  > It is powerful enough for production usage, but it's simple and hackable enough to be used for testing, local development, and learning. -Nevertheless, for realistically complex production use cases, it may be wiser to stand on the shoulders of some giant like [NGINX](https://www.nginx.com/) or [Apache](https://httpd.apache.org/) and that is exactly what we are going to do next: we are about to leverage NGINX to serve our Vue.js app because it is considered to be one of the most performant and battle-tested solutions out there.+Nevertheless, for realistically complex production use cases, it may be wiser to stand on the shoulders of some giant like [NGINX](https://www.nginx.com) or [Apache](https://httpd.apache.org).++That's exactly what we are going to do next. We are about to leverage NGINX to serve our Vue.js app because it is considered to be one of the most performant and battle-tested solutions out there.

Breaking the current sentence into two is a good idea, but do we really need paragraphs?

Zearin

comment created time in 4 days

pull request commentvuejs/vuejs.org

Update client-side-storage.md

Thanks!

TEnders64

comment created time in 4 days

push eventvuejs/vuejs.org

Todd Enders

commit sha 5c26fbd55cd2b1c1819e6d8476b3dad461d87449

Update client-side-storage.md (#2492)

view details

push time in 4 days

PR merged vuejs/vuejs.org

Update client-side-storage.md

Just a minor typo.

+1 -1

0 comment

1 changed file

TEnders64

pr closed time in 4 days

pull request commentvuejs/vuejs.org

fix: clarify how a Vue app works

Beautiful! Thanks @sarahdayan!

sarahdayan

comment created time in 4 days

push eventvuejs/vuejs.org

Sarah Dayan

commit sha efd804bf950485d8cbbcef32c67013000c1f172e

fix: clarify how a Vue app works (#2490) * fix: clarify how a Vue app works fixes #2475 * fix: simplify sentence * fix: remove unnecessary capitalization * fix: remove confusing wording

view details

push time in 4 days

PR merged vuejs/vuejs.org

fix: clarify how a Vue app works

This clarifies how a Vue app works, as discussed here.

@phanan I didn't use a tip block since I imagine it's not a good idea to overuse them; let me know if this kind of one-off paragraphs require one though 🙂

fixes #2475

+2 -0

0 comment

1 changed file

sarahdayan

pr closed time in 4 days

issue closedvuejs/vuejs.org

Misleading documentation - Section "Getting started"

I wasn´t able to find the right place to report my problem, so I decided to create an issue. Please feel free to tell me, where I should place problems like the following:

Yesterday I started working with vue.js. After reading and understanding the "Getting started" section (https://vuejs.org/v2/guide/index.html) I started developing. Now, my colleagues told me, that I did something wrong: For each div-container I created a new Vue instance. So instead of creating one application with many components I created many application without any components.

I told to my colleagues, that I exactly did, what the documentation says. And they aggreed: The docs suggests to create many applications, so it´s misleading.

It would be very nice, if someone could make this point clear in the documentation.

Thanks in advance

Patrick

closed time in 4 days

PatrickRoesler

pull request commentvuejs/vuejs.org

docs: Minor copy-edits and formatting tweaks

Amazing job @Zearin! Please allow us some time to go through all these changes, though 😅

Zearin

comment created time in 4 days

push eventphanan/unit-test-async-component

Renovate Bot

commit sha 1807a60ce44a2269489bf7d1c289e3442933f27d

Pin dependencies

view details

Phan An

commit sha cb45bc6789aea81cf7c6d05e50cc3a672b10c863

Merge pull request #2 from phanan/renovate/pin-dependencies Pin dependencies

view details

push time in 5 days

PR merged phanan/unit-test-async-component

Pin dependencies

This PR contains the following updates:

Package Type Update Change
@vue/cli-plugin-babel devDependencies pin ^3.6.0 -> 3.6.0
@vue/cli-plugin-eslint devDependencies pin ^3.6.0 -> 3.6.0
@vue/cli-plugin-unit-jest devDependencies pin ^3.6.0 -> 3.6.3
@vue/cli-service (source) devDependencies pin ^3.6.0 -> 3.6.0
@vue/eslint-config-standard devDependencies pin ^4.0.0 -> 4.0.0
babel-eslint devDependencies pin ^10.0.1 -> 10.0.1
babel-jest devDependencies pin ^23.6.0 -> 23.6.0
core-js dependencies pin ^2.6.5 -> 2.6.5
eslint (source) devDependencies pin ^5.16.0 -> 5.16.0
eslint-plugin-vue (source) devDependencies pin ^5.0.0 -> 5.2.2
node-sass devDependencies pin ^4.9.0 -> 4.12.0
sass-loader devDependencies pin ^7.1.0 -> 7.1.0
vue dependencies pin ^2.6.10 -> 2.6.10
vue-template-compiler devDependencies pin ^2.5.21 -> 2.6.10

:pushpin: Important: Renovate will wait until you have merged this Pin PR before creating any upgrade PRs for the affected packages. Add the preset :preserveSemverRanges your config if you instead don't wish to pin dependencies.


Renovate configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Whenever PR is stale, or if you tick the rebase/retry checkbox below.

:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

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

+75 -75

0 comment

2 changed files

renovate[bot]

pr closed time in 5 days

push eventphanan/smart-playlist-creator

Renovate Bot

commit sha 3ffd868e3978e05fdbbcb606fc8adc382a9314da

Pin dependencies

view details

Phan An

commit sha 5ef7de67bcf521cfe0eac37998f9c313a658aeb9

Merge pull request #2 from phanan/renovate/pin-dependencies Pin dependencies

view details

push time in 5 days

PR merged phanan/smart-playlist-creator

Pin dependencies

This PR contains the following updates:

Package Type Update Change
@vue/cli-plugin-babel devDependencies pin ^3.0.4 -> 3.0.5
@vue/cli-plugin-eslint devDependencies pin ^3.0.4 -> 3.0.5
@vue/cli-service (source) devDependencies pin ^3.0.4 -> 3.0.5
node-sass devDependencies pin ^4.9.4 -> 4.9.4
sass-loader dependencies pin ^7.1.0 -> 7.1.0
vue dependencies pin ^2.5.17 -> 2.5.17
vue-form-generator devDependencies pin ^2.3.1 -> 2.3.1
vue-template-compiler devDependencies pin ^2.5.17 -> 2.5.17

:pushpin: Important: Renovate will wait until you have merged this Pin PR before creating any upgrade PRs for the affected packages. Add the preset :preserveSemverRanges your config if you instead don't wish to pin dependencies.


Renovate configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Whenever PR is stale, or if you tick the rebase/retry checkbox below.

:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

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

+16 -16

0 comment

2 changed files

renovate[bot]

pr closed time in 5 days

push eventphanan/counter-meetup

dependabot[bot]

commit sha e914fbdb4ddf0e4d263eddc47ef4e5f1aabba0cd

chore(deps): bump nwmatcher from 1.4.3 to 1.4.4 Bumps [nwmatcher](https://github.com/dperini/nwmatcher) from 1.4.3 to 1.4.4. - [Release notes](https://github.com/dperini/nwmatcher/releases) - [Commits](https://github.com/dperini/nwmatcher/commits) Signed-off-by: dependabot[bot] <support@github.com>

view details

Phan An

commit sha d74b6869e674e930245bfb25f10f065aed5cf100

Merge pull request #3 from phanan/dependabot/npm_and_yarn/nwmatcher-1.4.4 chore(deps): bump nwmatcher from 1.4.3 to 1.4.4

view details

push time in 5 days

PR merged phanan/counter-meetup

chore(deps): bump nwmatcher from 1.4.3 to 1.4.4 dependencies

Bumps nwmatcher from 1.4.3 to 1.4.4. <details> <summary>Commits</summary>

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>

+2 -2

0 comment

1 changed file

dependabot[bot]

pr closed time in 5 days

push eventphanan/counter-meetup

dependabot[bot]

commit sha c095ffcae9cee920bf4c98655d96b320302dca8d

chore(deps): bump stringstream from 0.0.5 to 0.0.6 Bumps [stringstream](https://github.com/mhart/StringStream) from 0.0.5 to 0.0.6. - [Release notes](https://github.com/mhart/StringStream/releases) - [Commits](https://github.com/mhart/StringStream/compare/v0.0.5...v0.0.6) Signed-off-by: dependabot[bot] <support@github.com>

view details

Phan An

commit sha 5fe0c492d3996fd24cbcd8924e9b09a190b931c3

Merge pull request #4 from phanan/dependabot/npm_and_yarn/stringstream-0.0.6 chore(deps): bump stringstream from 0.0.5 to 0.0.6

view details

push time in 5 days

PR merged phanan/counter-meetup

chore(deps): bump stringstream from 0.0.5 to 0.0.6 dependencies

⚠️ Dependabot is rebasing this PR ⚠️

If you make any changes to it yourself then they will take precedence over the rebase.


Bumps stringstream from 0.0.5 to 0.0.6. <details> <summary>Commits</summary>

  • fee31c5 0.0.6
  • 2f4a9d4 Merge pull request #9 from mhart/fix-buffer-constructor-vuln
  • afbc744 Ensure data is not a number in Buffer constructor
  • See full diff in compare view </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>

+2 -2

0 comment

1 changed file

dependabot[bot]

pr closed time in 5 days

push eventphanan/counter-meetup

dependabot[bot]

commit sha b550bacca482fc4ec31c8283fadf1eba7bec843a

chore(deps-dev): bump webpack-dev-server from 2.9.7 to 3.1.11 Bumps [webpack-dev-server](https://github.com/webpack/webpack-dev-server) from 2.9.7 to 3.1.11. - [Release notes](https://github.com/webpack/webpack-dev-server/releases) - [Changelog](https://github.com/webpack/webpack-dev-server/blob/master/CHANGELOG.md) - [Commits](https://github.com/webpack/webpack-dev-server/compare/v2.9.7...v3.1.11) Signed-off-by: dependabot[bot] <support@github.com>

view details

Phan An

commit sha a6632fee0f21bcb4f24675d9af19ccc0c7d4f2b1

Merge pull request #6 from phanan/dependabot/npm_and_yarn/webpack-dev-server-3.1.11 chore(deps-dev): bump webpack-dev-server from 2.9.7 to 3.1.11

view details

push time in 5 days

PR merged phanan/counter-meetup

chore(deps-dev): bump webpack-dev-server from 2.9.7 to 3.1.11 dependencies

Bumps webpack-dev-server from 2.9.7 to 3.1.11. <details> <summary>Release notes</summary>

Sourced from webpack-dev-server's releases.

v3.1.11

<a name="3.1.11"></a>

3.1.11 (2018-12-21)

Bug Fixes

v3.1.10

2018-10-23

Bug Fixes

  • options: add writeToDisk option to schema (#1520) (d2f4902)
  • package: update sockjs-client v1.1.5...1.3.0 (url-parse vulnerability) (#1537) (e719959)
  • Server: set tls.DEFAULT_ECDH_CURVE to 'auto' (#1531) (c12def3)

v3.1.9

No release notes provided.

v3.1.8

2018-09-06

Bug Fixes

  • package: yargs security vulnerability (dependencies) (#1492) (8fb67c9)
  • utils/createLogger: ensure quiet always takes precedence (options.quiet) (#1486) (7a6ca47)

v3.1.7

2018-08-29

Bug Fixes

  • Server: don't use spdy on node >= v10.0.0 (#1451) (8ab9eb6)

v3.1.6

2018-08-26

Bug Fixes

</tr></table> ... (truncated) </details> <details> <summary>Changelog</summary>

Sourced from webpack-dev-server's changelog.

3.1.11 (2018-12-21)

Bug Fixes

<a name="3.1.10"></a>

3.1.10 (2018-10-23)

Bug Fixes

  • options: add writeToDisk option to schema (#1520) (d2f4902)
  • package: update sockjs-client v1.1.5...1.3.0 (url-parse vulnerability) (#1537) (e719959)
  • Server: set tls.DEFAULT_ECDH_CURVE to 'auto' (#1531) (c12def3)

<a name="3.1.9"></a>

3.1.9 (2018-09-24)

<a name="3.1.8"></a>

3.1.8 (2018-09-06)

Bug Fixes

  • package: yargs security vulnerability (dependencies) (#1492) (8fb67c9)
  • utils/createLogger: ensure quiet always takes precedence (options.quiet) (#1486) (7a6ca47)

<a name="3.1.7"></a>

3.1.7 (2018-08-29)

Bug Fixes

  • Server: don't use spdy on node >= v10.0.0 (#1451) (8ab9eb6)

</tr></table> ... (truncated) </details> <details> <summary>Commits</summary>

  • ff2874f chore(release): 3.1.11
  • b3217ca fix: check origin header for websocket connection (#1603)
  • 68dd49a fix: add url for compatibility with webpack@5 (#1598) (#1599)
  • fadae5d fix(Server): mime type for wasm in contentBase directory (#1575) (#1580)
  • 7a3a257 fix(package): update spdy v3.4.1...4.0.0 (assertion error) (#1491) (#1563)
  • 1fe82de ci(travis): Node 11 (on OS X) crashes, use 10 for now (#1588)
  • 55398b5 fix(bin/options): correct check for color support (options.color) (#1555)
  • 927a2b3 fix(Server): correct node version checks (#1543)
  • fa96a76 chore(PULL_REQUEST_TEMPLATE): allow features (#1539)
  • fe3219f chore(release): 3.1.10
  • Additional commits viewable in compare view </details> <details> <summary>Maintainer changes</summary>

This version was pushed to npm by evilebottnawi, a new releaser for webpack-dev-server since your current version. </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>

+1784 -607

0 comment

3 changed files

dependabot[bot]

pr closed time in 5 days

push eventphanan/counter-meetup

dependabot[bot]

commit sha fef0cf7dd56d15dcc055757782d581280ec9032c

chore(deps): bump diff from 3.4.0 to 3.5.0 Bumps [diff](https://github.com/kpdecker/jsdiff) from 3.4.0 to 3.5.0. - [Release notes](https://github.com/kpdecker/jsdiff/releases) - [Changelog](https://github.com/kpdecker/jsdiff/blob/master/release-notes.md) - [Commits](https://github.com/kpdecker/jsdiff/compare/v3.4.0...v3.5.0) Signed-off-by: dependabot[bot] <support@github.com>

view details

Phan An

commit sha 6336589c335756e10993ef6301bdf5f0c002c72a

Merge pull request #5 from phanan/dependabot/npm_and_yarn/diff-3.5.0 chore(deps): bump diff from 3.4.0 to 3.5.0

view details

push time in 5 days

PR merged phanan/counter-meetup

chore(deps): bump diff from 3.4.0 to 3.5.0 dependencies

Bumps diff from 3.4.0 to 3.5.0. <details> <summary>Changelog</summary>

Sourced from diff's changelog.

v3.5.0 - March 4th, 2018

  • Omit redundant slice in join method of diffArrays - 1023590
  • Support patches with empty lines - fb0f208
  • Accept a custom JSON replacer function for JSON diffing - 69c7f0a
  • Optimize parch header parser - 2aec429
  • Fix typos - e89c832

Commits </details> <details> <summary>Commits</summary>

  • e9ab948 v3.5.0
  • b73884c Update release notes
  • 8953021 Update release notes
  • 1023590 Omit redundant slice in join method of diffArrays
  • c72ef4a Add missing test coverage
  • b9ef24f Support patches with empty lines
  • 10aaabb Support patches with empty lines
  • 196d3aa Support patches with empty lines
  • e24d789 Support patches with empty lines
  • 8616a02 Support patches with empty lines
  • Additional commits viewable in compare view </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>

+2 -2

0 comment

1 changed file

dependabot[bot]

pr closed time in 5 days

push eventphanan/counter-meetup

Renovate Bot

commit sha 7b7fc75658eb329ee6fb932ae1d677feff8d4db4

Pin dependencies

view details

Phan An

commit sha e14e7fb85895bd62d2efe6e2edd4fe276c62c58f

Merge pull request #2 from phanan/renovate/pin-dependencies Pin dependencies

view details

push time in 5 days

PR merged phanan/counter-meetup

Pin dependencies

This PR contains the following updates:

Package Type Update Change
@vue/test-utils devDependencies pin ^1.0.0-beta.11 -> 1.0.0-beta.12
babel-core (source) devDependencies pin ^6.26.0 -> 6.26.0
babel-jest devDependencies pin ^21.2.0 -> 21.2.0
babel-loader devDependencies pin ^7.1.2 -> 7.1.2
babel-preset-env (source) devDependencies pin ^1.6.0 -> 1.6.1
cross-env devDependencies pin ^5.0.5 -> 5.1.3
css-loader devDependencies pin ^0.28.7 -> 0.28.7
file-loader devDependencies pin ^1.1.4 -> 1.1.6
jest (source) devDependencies pin ^22.4.2 -> 22.4.2
jest-serializer-vue devDependencies pin ^0.2.0 -> 0.2.0
sinon (source) devDependencies pin ^4.4.2 -> 4.4.2
vue dependencies pin ^2.4.4 -> 2.5.13
vue-jest devDependencies pin ^1.0.0 -> 1.4.0
vue-loader devDependencies pin ^13.0.5 -> 13.6.1
vue-server-renderer devDependencies pin ^2.4.4 -> 2.5.13
vue-template-compiler devDependencies pin ^2.4.4 -> 2.5.13
vue-test-helpers devDependencies pin ^1.0.10 -> 1.0.10
webpack devDependencies pin ^3.6.0 -> 3.10.0
webpack-dev-server devDependencies pin ^2.9.1 -> 2.9.7

:pushpin: Important: Renovate will wait until you have merged this Pin PR before creating any upgrade PRs for the affected packages. Add the preset :preserveSemverRanges your config if you instead don't wish to pin dependencies.


Renovate configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Whenever PR is stale, or if you tick the rebase/retry checkbox below.

:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

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

+7120 -3545

0 comment

3 changed files

renovate[bot]

pr closed time in 5 days

push eventphanan/vue-snippets

Renovate Bot

commit sha 7606cb5b9092d06958c5a8e0f517a1df7627413f

Update dependency atomic-algolia to v0.3.17

view details

Phan An

commit sha 7fafbc898b1b9aefcf2a284d7dfad814274bb997

Merge pull request #5 from phanan/renovate/atomic-algolia-0.x Update dependency atomic-algolia to v0.3.17

view details

push time in 5 days

PR merged phanan/vue-snippets

Update dependency atomic-algolia to v0.3.17

This PR contains the following updates:

Package Type Update Change
atomic-algolia devDependencies patch 0.3.15 -> 0.3.17

Release Notes

<details> <summary>chrisdmacrae/atomic-algolia</summary>

v0.3.17

Compare Source

v0.3.16

Compare Source

</details>


Renovate configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Whenever PR becomes conflicted, or if you tick the rebase/retry checkbox below.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

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

+1737 -739

0 comment

2 changed files

renovate[bot]

pr closed time in 5 days

push eventphanan/factoria

Renovate Bot

commit sha 43607c5675141451bdac2ed5b3232f85c9aa7e84

chore(deps): update dependency rollup to v1.31.1

view details

Phan An

commit sha d42e1c2ede1ea74d8b6f30921efb9f2198af54af

Merge pull request #14 from phanan/renovate/rollup-1.x chore(deps): update dependency rollup to v1.31.1

view details

push time in 5 days

PR merged phanan/factoria

chore(deps): update dependency rollup to v1.31.1

This PR contains the following updates:

Package Type Update Change
rollup devDependencies patch 1.31.0 -> 1.31.1

Release Notes

<details> <summary>rollup/rollup</summary>

v1.31.1

Compare Source

2020-02-14

Bug Fixes
  • Make sure errored files are always re-evaluated in watch mode to avoid an issue in the typescript plugin (#​3388)
Pull Requests

</details>


Renovate configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Whenever PR becomes conflicted, or if you tick the rebase/retry checkbox below.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

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

+1 -1

0 comment

1 changed file

renovate[bot]

pr closed time in 5 days

push eventphanan/koel

dependabot-preview[bot]

commit sha 774855f54d971b49e765a2979a5664241273e84e

chore(deps-dev): bump facebook/webdriver from 1.8.0 to 1.8.1 (#1183) Bumps [facebook/webdriver](https://github.com/php-webdriver/php-webdriver) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/php-webdriver/php-webdriver/releases) - [Changelog](https://github.com/php-webdriver/php-webdriver/blob/master/CHANGELOG.md) - [Commits](https://github.com/php-webdriver/php-webdriver/compare/1.8.0...1.8.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

push time in 5 days

PR merged phanan/koel

chore(deps-dev): bump facebook/webdriver from 1.8.0 to 1.8.1 dependencies

Bumps facebook/webdriver from 1.8.0 to 1.8.1. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/php-webdriver/php-webdriver/blob/master/CHANGELOG.md">facebook/webdriver's changelog</a>.</em></p> <blockquote> <h2>1.8.1 - 2020-02-17</h2> <h3>Fixed</h3> <ul> <li>Accept array as possible input to <code>sendKeys()</code> method. (Unintentional BC break in 1.8.0.)</li> <li>Use relative offset when moving mouse pointer in W3C WebDriver mode.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/php-webdriver/php-webdriver/commit/262ea0d209c292e0330be1041424887bbbffef04"><code>262ea0d</code></a> Release version 1.8.1</li> <li><a href="https://github.com/php-webdriver/php-webdriver/commit/073a170b8b5f337c2b4eebf00057d346887e5697"><code>073a170</code></a> Normalize composer.json</li> <li><a href="https://github.com/php-webdriver/php-webdriver/commit/4c4bae3eaa1a474db8bc2d36b673d1e1681cb9ef"><code>4c4bae3</code></a> Reference phpunit.xsd from vendor to make it always up-to-date</li> <li><a href="https://github.com/php-webdriver/php-webdriver/commit/639cb48fbc575f73d73c3b02eb3c2512052caebb"><code>639cb48</code></a> Exclude skipped tests on SauceLabs</li> <li><a href="https://github.com/php-webdriver/php-webdriver/commit/739d2fc13787f810f7bcf9d54428a44b91eee9a7"><code>739d2fc</code></a> Add functional tests for keys actions</li> <li><a href="https://github.com/php-webdriver/php-webdriver/commit/7f8382892cb34118700c8544e4a03366efbcc50f"><code>7f83828</code></a> Fix mouse move action in W3C mode to use relative offset (fixes <a href="https://github-redirect.dependabot.com/php-webdriver/php-webdriver/issues/757">#757</a>)</li> <li><a href="https://github.com/php-webdriver/php-webdriver/commit/f6fe710c7160d3058016f3caf66a9a7fef61f36c"><code>f6fe710</code></a> Add functional tests for dragAndDrop actions</li> <li><a href="https://github.com/php-webdriver/php-webdriver/commit/e8c0f60e0ed9d639d7e40c5bbefe7786c26694bc"><code>e8c0f60</code></a> Use constants when referencing mouse buttons</li> <li><a href="https://github.com/php-webdriver/php-webdriver/commit/6ee357444f5050feac2e11aaf83cd6130931a09b"><code>6ee3574</code></a> Edge on Sauce Labs started to misidentify itself back and is failing the build</li> <li><a href="https://github.com/php-webdriver/php-webdriver/commit/7729633d3b7068a62e76adc4b784eb78f8dec9ec"><code>7729633</code></a> Fix sendKeys not accepting array as input (<a href="https://github-redirect.dependabot.com/php-webdriver/php-webdriver/issues/759">#759</a>)</li> <li>See full diff in <a href="https://github.com/php-webdriver/php-webdriver/compare/1.8.0...1.8.1">compare view</a></li> </ul> </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
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+9 -9

0 comment

1 changed file

dependabot-preview[bot]

pr closed time in 5 days

push eventkoel/core

dependabot[bot]

commit sha e1fae43e00b6ba70f6a34ad14855f678e0aa9d9e

chore(deps-dev): bump codecov from 3.1.0 to 3.6.5 Bumps [codecov](https://github.com/codecov/codecov-node) from 3.1.0 to 3.6.5. - [Release notes](https://github.com/codecov/codecov-node/releases) - [Commits](https://github.com/codecov/codecov-node/commits) Signed-off-by: dependabot[bot] <support@github.com>

view details

Phan An

commit sha 41fe2c3c065a1a2daf7ed2ffbce9621277a273e4

Merge pull request #30 from koel/dependabot/npm_and_yarn/codecov-3.6.5 chore(deps-dev): bump codecov from 3.1.0 to 3.6.5

view details

push time in 5 days

PR merged koel/core

chore(deps-dev): bump codecov from 3.1.0 to 3.6.5 dependencies

Bumps codecov from 3.1.0 to 3.6.5. <details> <summary>Release notes</summary>

Sourced from codecov's releases.

v3.6.4

Fix for Cirrus CI

v3.6.3

AWS Codebuild fixes + package updates

v3.6.2

command line args sanitised

v3.6.1

Fix for Semaphore

v3.6.0

AWS CodeBuild Semaphore v2

v3.3.0

Added pipe --pipe, -l </details> <details> <summary>Commits</summary>

  • See full diff in compare view </details> <details> <summary>Maintainer changes</summary>

This version was pushed to npm by drazisil, a new releaser for codecov since your current version. </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>

+89 -28

0 comment

2 changed files

dependabot[bot]

pr closed time in 5 days

Pull request review commentvuejs/vuejs.org

fix: clarify how a Vue app works

 var app = new Vue({  We have already created our very first Vue app! This looks pretty similar to rendering a string template, but Vue has done a lot of work under the hood. The data and the DOM are now linked, and everything is now **reactive**. How do we know? Open your browser's JavaScript console (right now, on this page) and set `app.message` to a different value. You should see the rendered example above update accordingly. +Note that we no longer have to interact with the HTML directly. A Vue app attaches itself to a single, global DOM element (`#app` in our case) then fully controls it. The HTML is our entry point, but everything else happens within the newly created Vue instance.

This is great! I have but one tiny issue: What's a global DOM element? Can/should we refer to it more simply as a "single DOM element" to keep beginners from getting further confused?

sarahdayan

comment created time in 5 days

pull request commentvuejs/vuejs.org

Update forms.md

This is absolutely beautiful, thanks @Zearin!

Zearin

comment created time in 5 days

push eventvuejs/vuejs.org

Zearin

commit sha df72c7e3d50d6ae76f96ed54ef0f5e8e66101b0e

Update forms.md (#2489) Minor copy edits and formatting tweaks

view details

push time in 5 days

PR merged vuejs/vuejs.org

Update forms.md

Minor copy edits and formatting tweaks

+11 -9

0 comment

1 changed file

Zearin

pr closed time in 5 days

issue commentvuejs/vuejs.org

Misleading documentation - Section "Getting started"

Do you think there would be value in explaining more about what is a Vue app and how it attaches itself to a single global DOM element, then fully controls it?

Yeah, I think this might be beneficial for beginners who are absolutely new to a framework. Do you reckon this paragraph can be written in a way that conveys our new message too?

We have already created our very first Vue app! This looks pretty similar to rendering a string template, but Vue has done a lot of work under the hood. The data and the DOM are now linked, and everything is now reactive. How do we know? Open your browser’s JavaScript console (right now, on this page) and set app.message to a different value. You should see the rendered example above update accordingly.

A PR is most welcome naturally :)

PatrickRoesler

comment created time in 5 days

startednuwave/lighthouse

started time in 5 days

pull request commentkoel/koel-aws

Support for .flac files for koel parity

Thanks!

Inkybro

comment created time in 6 days

push eventkoel/koel-aws

Ethan Barron

commit sha 0c01637c41cb8696bc56ad1ff2a5f2414b5c8e26

Support for .flac files for koel parity

view details

Phan An

commit sha d279f28dbce5189bf3213f756d2ce6b0f2d1560d

Merge pull request #11 from Inkybro/support-flac-files Support for .flac files for koel parity

view details

push time in 6 days

PR merged koel/koel-aws

Support for .flac files for koel parity

Noticed that flac isn't included as a supported filetype, but Koel has (limited) support. Feel free to take this or not.

+1 -1

0 comment

1 changed file

Inkybro

pr closed time in 6 days

issue commentvuejs/vuejs.org

Misleading documentation - Section "Getting started"

The main reason why the IDs are different across the page is that the exact same scripts are executed under the hood (you can verify this by looking at the page's source code). Using only 'app' would break this connection.

As said above, this literally is the first time we/I have this feedback. TBH, personally I don't see this as an issue and am tempting to close it unless more people say otherwise.

PatrickRoesler

comment created time in 6 days

issue commentvuejs/vuejs.org

📢 Community translation announcements

@nkoehring @Phosphenius @thilobillerbeck As mentioned in the original post, can you folks discuss the project in its own repository? Thanks!

phanan

comment created time in 7 days

pull request commentvuejs/vuejs.org

Update state-management.md #2

Thanks!

adamwirth

comment created time in 9 days

push eventvuejs/vuejs.org

Adam Wirth

commit sha fd246eb29e947bb9c8861d8367acd8af298b7945

Update state-management.md #2 (#2488) use `var` consistently. previous PR was using `const`, it should be using `var`. ref: https://github.com/vuejs/vuejs.org/pull/2486#issuecomment-588314467

view details

push time in 9 days

PR merged vuejs/vuejs.org

Update state-management.md #2

Use var consistently. previous PR was using const, it should be using var.

Ref: https://github.com/vuejs/vuejs.org/pull/2486#issuecomment-588314467

+3 -3

0 comment

1 changed file

adamwirth

pr closed time in 9 days

pull request commentvuejs/vuejs.org

Update state-management.md

@adamwirth Indeed! Would you want to send a PR for it?

adamwirth

comment created time in 9 days

created repositoryphanan/in-cms

created time in 9 days

more