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.

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

Description

The referenced page describes the following:

Directives that behave like *ngIf can declare that they want the same treatment by including a static member marker that is a signal to the template compiler to treat them like *ngIf. This static member for *ngIf is:
public static ngIfUseIfTypeGuard: void;

It's not very clear that the pattern has to be `xyzUse

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

When building and running storybook I would like to be able to pass parameters for angular.json. For instance injecting configurations in Angular is done with "ng serve -c my-config" or "ng build -c my-config" and I would like to do the same when running Angular inside storybook.

As Angular does not support environment variables that is not an option.

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 resolutions field in package.json, pkg: "1.0.0"
upd

JavaScript

Here are 133,209 public repositories matching this topic...

freeCodeCamp / freeCodeCamp

vuejs / vue

facebook / react

twbs / bootstrap

getify / You-Dont-Know-JS

airbnb / javascript

electron / electron

axios / axios

nodejs / node

justjavac / free-programming-books-zh_CN

mrdoob / three.js

trekhleb / javascript-algorithms

microsoft / TypeScript

angular / angular

Description

30-seconds / 30-seconds-of-code

Description

mui-org / material-ui

webpack / webpack

atom / atom

expressjs / express

chartjs / Chart.js

storybookjs / storybook

h5bp / html5-boilerplate

ElemeFE / element

lodash / lodash

meteor / meteor

ionic-team / ionic

yarnpkg / yarn

FreeCodeCampChina / freecodecamp.cn

thedaviddias / Front-End-Checklist

Dogfalo / materialize

Related Topics