Skip to content
#

Node.js

nodejs logo

Node.js is a tool for executing JavaScript in a variety of environments. JavaScript had humble beginnings as a language that lived only in web browsers, but the Node.js project has expanded its reach and helped make it the most popular programming language in the world. Node.js extends the creative potential of people with web development experience, enabling a new generation of developers to create servers, command-line tools, desktop apps, and even robots.

Here are 83,979 public repositories matching this topic...

freeCodeCamp
electron
sadokmtir
sadokmtir commented Jan 21, 2020

I think it is worth mentioning that the solution stated Catching unresolved and rejected promises is not always valid. what I mean is that if a promise is caught on a later turn of the Node.js event loop, then probably throwing an error on this global catch is not a good idea. I am wondering how this is counted as best practice while obviously from the node official documentation it should

dooglio
dooglio commented Jul 3, 2018
  • Operating system and version:
    Mac OS/X High Sierra

  • nvm debug output:

nvm --version: v0.33.11
$TERM_PROGRAM: Apple_Terminal
$SHELL: /bin/bash
$SHLVL: 1
$HOME: /Users/doug
$NVM_DIR: '$HOME/.nvm'
$PATH: $NVM_DIR/versions/node/v10.4.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/VMware Fusion.app/Co
li000306
li000306 commented Mar 11, 2020

注意:这里只处理 FreeCodeCamp.cn 的相关问题,不处理 w3cschool 的任何问题

注意:请不要乱开无意义的 Issue,违者直接加黑名单

注意:Issue 是用来处理代码库中的 bug,不是用来提问题的。完成挑战过程中遇到的代码问题请在gitter 讨论组 或者 QQ 群 526289580 中讨论 (QQ 群验证答案: freeCodeCamp 注意大小写)

FreeCodeCamp.cn Issue 模板

如何使用本模板:

  • 尽可能多填些相关信息,方便管理员参考
  • 对于无法给出的内容,请删除掉那一行

以上内容请在提交 Issue 之前删除

浏览器信息

  • 浏览器名称,版本号
  • 操作系统
Ghost
formerandroider
formerandroider commented Dec 18, 2019

Issue Summary

In Safari 13.0.4 on macOS 10.15.2, the 'Upload routes YAML' button triggers a file browser that only allows selection of files ending in .yml. These are not accepted by the application, which requires a .yaml extension. This results in routes not being uploadable with Safari.

To Reproduce

  1. In Safari, click the 'Upload routes YAML' button in Labs.

This doesn'

locopati
locopati commented Apr 13, 2020

Describe the bug
I want to clear the date that was set on a field

Steps to reproduce the behavior

  1. Create a type with a date field that is not required
  2. Create an instance of the type with a value in the date field and save it
  3. Edit the instance and clear the date field
  4. It cannot be cleared
  5. Make a GraphQL request to clear the field
  6. The request errors

**Expecte

feross
feross commented Sep 14, 2019

https://eslint.org/docs/rules/computed-property-spacing

Current rule:

"computed-property-spacing": ["error", "never"],

Proposed rule:

"computed-property-spacing": ["error", "never", { "enforceForClassMembers": true }],

By default, this rule does not check class declarations and class expressions,
as the default value for enforceForClassMembers is false.

W

trollepierre
trollepierre commented Mar 28, 2020

Hello,

In the docs, we are mentioning a { weekStartsOn: 1 } argument to choose the day of the week
https://date-fns.org/v2.11.1/docs/differenceInCalendarWeeks

In that file, I see the comment about it. But this argument has no impact about my test.
https://github.com/date-fns/date-fns/blob/master/src/differenceInCalendarWeeks/index.js

while testing the example, I got -3 instead of

sheetjs
langpavel
langpavel commented Oct 24, 2017

Too wide (and falsy) segregation of GraphQL Types and Resolvers

The first example of this is new ObjectType in src/data/queries/index.js importing fields.
Fields should be taken in context of parent type, not as standalone information.

This can ensure some users that custom types cannot have own field resolvers which is false.

In fact, much of fields which can have own resolvers

boneskull
boneskull commented Apr 14, 2020

I'm getting bit with failing documentation builds because I'm writing docstrings that JSDoc doesn't like (specifically, TS-style). But there's no linting happening before getting to Netlify.

We may be able to make JSDoc just check the syntax and exit (and make it part of the lint scripts).

This is moot if we want to move forward with maintaining our own TS types (for which there is an op

ava
sunshineo
sunshineo commented Apr 9, 2020

Is your feature request related to a problem? Please describe.
Deployed Parse server using k8 and used /parse/health for the readinessProbe and livenessProbe probe. But when deploy new code and broke the database connection, /parse/health still returns 200 OK. So old container was killed and new broken one brought online

Describe the solution you'd like
Only return 200 ok after db is

Created by Ryan Dahl

Released May 27, 2009

Organization
nodejs
Website
nodejs.org/en
Wikipedia
Wikipedia
You can’t perform that action at this time.