In What about &&? section we have the following code.

function foo() {
    console.log( a );
}

var a = 42;

a && foo(); // 42

result in comment should indicate that foo was called. but in fact we would get same result of "42" if first operand had been called (like in || operator). i think results of a and foo() should be different to make the example be clearer.

The max-classes-per-file rule is enabled in rules/best-practices.js but there is no mention of this requirement in the docs. If this is a best practice, I'd like to know why.

Feature request

Support optionalDependencies as NPM and Yarn do:
http://npm.github.io/using-pkgs-docs/package-json/types/optionaldependencies.html
https://yarnpkg.com/lang/en/docs/dependency-types/

It's useful for example when you need to use an package in Windows and other in Mac/Linux and packages support os t

Feature Request

![](https://example.com/you-know-how-excited-i-am.gif)

This means that it should be enabled via shippedProposals: true options in @babel/preset-env 🎉

It should be done similarly to this commit: https://github.com/babel

🙋 feature request

https://github.com/parcel-bundler/parcel/blob/d24e09a9797af41a9d2c6c733b1c6cf6671d60c7/packages/core/workers/src/Profiler.js#L2

The inspector module not always available, it depends on build param --without-inspector

🤔 Expected Behavior

Compatible with --without-inspector mode.

😯 Current Behavior

Direct import

💁 Possible Solution

Not pretty

When I check during update Korean translate of 33-js-concepts, I found some typo like below.

ESLint supports the notion of "processors" which allows us to extract JS from markdown files and lint it to ensure it is in standard style. https://eslint.org/docs/user-guide/configuring#specifying-processor

That would let us eliminate this whole section of the readme which describes how to install eslint-plugin-markdown, run standard with the --plugin flag. In the end you need to actuall

Describe the bug
Email templates can be managed directly in Mailgun. But the related Strapi provider doesn't support them.
M

In order to provide the most up-to-date information for react-redux links metadata should be included for the articles. My suggestion would be to add the dates the articles were published. If this is something you're interested in let me know and I can submit a PR.

The contributing guidelines need to be fixed immediately. Issue creation guideline specially. We need to enforce adding label as one of the behaviours while creating a new issue.

cc- @tsov

Tell me about your development environment.

> node --version
v8.9.4
> npm --version
5.6.0
> # And I'm running Windows 10.

Describe the issue / bug.

Setting extraResources in package.json (docs), like this --

"build": {
	"extraResources: [
		"dir-to-include-as-a-resource"
	]
}

In dialog intended to encourage new user to choose an appropriate theme for their business, if you choose BUSINESS, then WEB DESIGN, then select the “CALM” design option, the subhead text “Welcome! What can we do for you today?” is far too large for the containing block (especially in mobile preview view). The subhead is also set in white, and superimposed over a photo containing large swaths of w

Like it's done for Samsung Internet and other browsers, see this and this files.

I have no ideas where I can find the data source, so required your help.

• I've read the guidelines for Contributing to Roots Projects
• This request isn't a duplicate of an existing issue
• I've read the docs and followed them (if applicable)
• This is not a personal support request that should be posted on the [Roots Discourse](https://discourse.roots

can you provide documentation for triggers / events handling like copy, cut, paste , merge cell, changing color for specific cell etc. thanks @myliang

• I'm submitting a ...

  • bug report
  • feature request

• What is the motivation / use case for changing the behavior?

https://github.com/epicmaxco/vuestic-admin/blob/2a64ca23d0b462e5b4cbdf03570a45ccb69850cb/src/components/admin/AppLayout.vue#L15

I suggest the specific layout styles should be defined in routes instead of the main layout.
Any ideas?

This is a reminder for loadimpact/k6#1162

configDir is a copy of os.UserConfigDir to support pre go1.12, it should be removed and use os.ConfigDir directly from go1.13 onward.

Hi there,

The https://glidejs.com/docs/extending page sends a 404.
The dead link can be found on the https://glidejs.com/docs/ in the "Extended section".
Here is a screenshot:

Cordially,
Cyril

• bizcharts Version: any
• Platform or react version: any
• Mini Showcase(like screenshots):
• CodePen Link: https://codepen.io/anon/pen/zgwdRE

retro step:

1. click "toggle tooltip", tooltip change to sticky mode.
2. click "toggle tooltip", tooltip should recover default config, but it not.

From the docs:

.mjs files are limited to basic functionality without support for esm options.

I'm converting a package to esm. Having converted all the src files to esm syntax, but keeping the file extensions as .js, everything works ok. However, if I rename some src files to .mjs I get errors importing other packages:

I couldn't find any place in the documentation that would showcase all possible configurational parameters that can be used inside backpack.config.js file. Is it possible to add not only config.entry.main but also showcase all other available options with a brief explanation of its purpose?