JavaScript
JavaScript (JS) is a lightweight interpreted or JIT-compiled programming language with first-class functions. While it is most well-known as the scripting language for Web pages, many non-browser environments also use it, such as Node.js, Apache CouchDB and Adobe Acrobat. JavaScript is a prototype-based, multi-paradigm, dynamic language, supporting object-oriented, imperative, and declarative (e.g. functional programming) styles.
Here are 134,552 public repositories matching this topic...
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Updated
Dec 19, 2019 - JavaScript
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Updated
Dec 19, 2019 - JavaScript
The most popular HTML, CSS, and JavaScript framework for developing responsive, mobile first projects on the web.
-
Updated
Dec 19, 2019 - JavaScript
A book series on JavaScript. @YDKJS on twitter.
-
Updated
Dec 19, 2019
:electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
-
Updated
Dec 19, 2019 - C++
Promise based HTTP client for the browser and node.js
-
Updated
Dec 19, 2019 - JavaScript
Currently when using the --experimental-resolve-self flag, with the following:
{
"name": "test",
"exports": "./test.js"
}If including a require('test') in the test.js file and running node --experimental-resolve-self pkg/test.js this will throw an error.
It works with "main" and exports subpaths though so may be a sugar-specific or main-specific error case fo
I think it makes more sense to return an empty array
// invalid input return null or throw an error
if (!setA || !setB) {
return null;
}
if (!setA.length || !setB.length) {
return [];
}
// or do nothing since the for loop will not trigger anyway
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
Updated
Dec 19, 2019 - TypeScript
Description
So our function arrayToHtmlList is in a pretty bad space and could use an update. We already had some discussion over at #675 but I wanted to move the update discussion over to an issue for more visibility.
Current problem:
It uses an awkward query selector instead of the `document.prototype.getElementBy
React components for faster and easier web development. Build your own design system, or start with Material Design.
-
Updated
Dec 19, 2019 - JavaScript
A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
-
Updated
Dec 19, 2019 - JavaScript
Fast, unopinionated, minimalist web framework for node.
-
Updated
Dec 19, 2019 - JavaScript
Is your feature request related to a problem? Please describe.
I would like to be able to configure the iframe width in the same way I can already configure the height.
Describe the solution you'd like
To add a parameter similar to iframeHeight that will configure the width of the iframe. Ideal name would be iframeWidth
Describe alternatives you've considered
Any other met
A professional front-end template for building fast, robust, and adaptable web apps or sites.
-
Updated
Dec 19, 2019 - JavaScript
Element UI version
2.12.0
OS/Browsers version
MacOS / Chrome 76
Vue version
2.5.12
Reproduction Link
https://codepen.io/smk0621-the-selector/pen/MWgGzqO
Steps to reproduce
- Set display style for input-number
- Hover in number button of each side of input-number
- we will see that border c
A modern JavaScript utility library delivering modularity, performance, & extras.
-
Updated
Dec 19, 2019 - JavaScript
Do you want to request a feature or report a bug?
feature request
What is the current behavior?
Currently yarn why won't indicate any package info in the resolutions field
If the current behavior is a bug, please provide the steps to reproduce.
- install a package with any version, e.g
"pkg": "^1.0.0" - add
resolutionsfield in package.json,pkg: "1.0.0" - upd
:white_check_mark: The largest Node.js best practices list (December 2019)
-
Updated
Dec 19, 2019 - JavaScript
The Head section says:
The next 2 meta tags (Charset and Viewport) need to come first in the head.
I found a reference for Charset being early on in the head:
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta
The
<meta>element declaring the encoding must be inside the<head>element and within the first 1024 bytes of the HTML as some browsers only look at those bytes be
Created by Brendan Eich
Released December 4, 1995
- Website
- developer.mozilla.org/en-US/docs/Web/JavaScript
- Wikipedia
- Wikipedia
The GIF over here depicts fCC in its old design. Even though I don't think there's anything wrong with it, I guess it should be updated to align with how fCC looks now
![image](https://user-images.githubusercontent.com/34807532/70627002-6e7c8280-1c4b-11ea-87d