🎉🎉 The Node.js best practices guide has gotten even better during September and October, thanks to the many awesome contributions made by the following folks 🎉🎉

📢 🇷🇺 Our guide is now also translated to Russian (+ other 8 languages)! This thanks to the AMAZING work of Alex Ivanov @contributorpw ❤️

The following folks suggested & contributed great new ideas and enhancements:
🌻 Adeel Imran @A

Hello! Big fan of enzyme here.

I use Enzyme a lot for unit testing and I've noticed recently that people are consistently recommending people use instance prop functions versus using the simulate behavior provided by Enzyme because of the bad implementation.

Is there anyway we could get the docs updated with what the preferred solution is? It's not really clear as the docs stand right now.

Type of issue: (feature suggestion, bug?)

Suggestion

Chapter:

no-chapter

Why use .jsx instead of .js? It's not a best practice: facebook/create-react-app#87 (comment)

Hi, I'm a Redux maintainer. I'd like to offer a couple suggestions.

Problem

The current Redux example implementation shows use of reducers with "hand-written" immutable update logic, and has a somewhat complex store configuration. In addition, the project currently uses a "folder-by-type" folder structure.

Proposed Solution

The project should switch to using the official [Redux

The second example in section 1.1 says:

expect(result.approved).to.be.false;

It should be:

expect(result.approved).to.be.true;

(I'm guessing you made it false so you could simulate the error output in the next picture.)

Is this a bug report or a feature request?

Feature request

Version Info

• Version of Majestic: 1.6.1
• Version of Jest: 24.9.0
• Version of Node: 8.9.4
• Operating System: Mac OS X

Reproduction Repo

I want to use this testing tool in my company, But someone ask me that change majestic logo in sidebar. I thought that change logo option is useful for company test server. C

how can add a new module,

1. npm install -g plop
2. run plop $ plop module
3. also fine ... `
   ? Module name (Casing will be modified) chat
   ? Module name (Casing will be modified) chat
   [SUCCESS] add \src\modules\chat\ChatState.js
   [SUCCESS] add \src\modules\chat\ChatView.js
   [SUCCESS] add \src\modules\chat\ChatViewContainer.js
   [SUCCESS] modify \src\redux\reducer.js
   [SUCCESS] modify \src

I download the ZIP and run npm install but then I run expo start and I get:

[11:17:11] Starting project at /Volumes/Sata/repositories/snowflake copy
[11:17:12] Expo DevTools is running at http://localhost:19002
[11:17:12] Error: Missing app.json. See https://docs.expo.io/
[11:17:12] No Expo configuration found. Are you sure this is a project directory

How I solve this?

Th

Current Behavior

If you're on Node 8 you get errors when trying to run tsdx create, but the reason for the failures are unclear.

nvm use 8.11.3

npx tsdx create bar

Failed to install dependencies
Error: Command failed with exit code 1: yarn add @types/jest @types/react @types/react-dom husky react react-dom tsdx tslib typescript --dev

Issue :

The Paths Mapping section of the documentation suggests using the native node require but this fails with a Syntax Error when

Expected

• Platform: MacOS
• Mercury Parser Version: master
• Node Version (if a Node bug): v11.1.0
• Browser Version (if a browser bug): n/a

Description

I have created a custom extractor for https://www.gruene.de/themen/arbeit which delivers the expected results for content and lead_image_url with the following specifications:

export const WwwGrueneDeExt

Travis CI already has a builtin gh-pages deployment feature:

https://docs.travis-ci.com/user/deployment/pages/

Maybe we could use it instead of maintaining gh-page publish script, which makes the codebase more clear

Willing to submit a PR if you have the plan

I'd like to use jest-puppeteer pretty much like Jest + JSDOM, I will not test real web pages, but I need the real DOM APIs to test some code.

I would like to have access to window and/or document globally, how can I do?

This is my Jest config:

  "jest": {
    "preset": "jest-puppeteer",
    "testMatch": ["**/src/**/*.test.js"],
    "globalSetup": "jest-environment-puppetee

@diegohaz - i noticed a couple of minor spelling errors on the main site:

Basic stack
It includes everything necessary to build a tipical web app with focus on productivity and developer experience.
Learn more about the recomended workflow

Should be typical, and recommended.

Just an FYI.

Thanks!

I was noticing that when running jest with the --no-color flag, jest-image-snapshot was still using color. It looks like this is due to code introduced in #5 to solve the same issue that running jest with the --no-color flag would do. IMHO, all colorization should be consistent across all tests and handled at the jest level, not specified per expect() invocation.

Wanted to make sure tha

vue-tooltip component sometimes is hidden because of the overflow of the parent element (i.e modal)

.

Hi Team, nice examples!

basics/hover.js example

For me I have to add a sleep() function to make sure await page.screenshot({ path: 'hover.png' }) can capture the hover effect.

const puppeteer = require('puppeteer');

function sleep(ms) {
  return new Promise(resolve => {
    setTimeout(resolve, 

In the 7-th chapter Higher Order Components section has a wrong link for 5-th example ( both Demo and Source code links are incorrect )

Instead of proper link for demo and [proper link for source code](https://github.com/MoonHighway/learning-react/blob/master/chapter-07/05-higher-order-com

If the extension crashes, such as due to process.exit() in a test, or deleting .bin/jest, then the extension will stop, as expected. But then the command Jest: Start Runner doesn't do anything; even if the ext is stopped, I still have to run Jest: Stop Runner, and then run Start Runner, for it to run.

Some folks have noted it would be beneficial to have this repository translated to other languages. One contributor has already volunteered to translate the repository into Russian (woohoo!).

If anyone has the time and drive to help out with other languages, please reply below with the proposed language and I'll give you the "go-ahead"... just to make sure two people don't create translations i

I can obtain record list (in JSON) from server.
jsonTypes handler passes if record list is filled with designated items.
However jsonTypes handler seems to disallow empty record list: Expected '*' not found (path 'records.*')

repro/test.js:

const frisby = require('frisby'),
  Joi = frisby.Joi;

it('should pass', (done) => {
  frisby.fromJSON({ records: [] })
    .inspectBody()

It looks like sendgrid is currently only used to reset user passwords. If that is the case it would be nice to have it also used to send a confirmation email upon user registration, so that it can be properly validated.

I suppose this would require the use of a unique email validation token.

When building Android app for production build I get this lint error. Its because generator builds only folders drawable-land-xxxx and drawable-port-xxx. There should be build also default drawable-xxxx folders I think.

Temporary solution is suppress this lint error adding this code to android/app/build.gradle

application {
....
 lintOptions{
   disable 'MissingDefaultResourc

Describe the feature you'd like:

Being new to testing-library, it all is a bit overwhelming. The long list of matchers jest-dom introduces, also makes it harder to start out.

Suggested implementation:

Group the matchers in the documentation over some headings, e.g. “Checking element existence”, “Checking forms”, “Checking element state”.

Describe alternatives you've cons

Feature Request

Description:
API for Date matchers. Some matchers are inspired by Jasmine Matchers.

Possible solution:

Jasmine-like matchers:

expect(date).toBeDate(); // Matcher added
expect(date).toBeValidDate();  // Matcher added

expect(date).toBeAfter(otherDate); // Matcher added
expect(date).toBeBefore(otherDa

Just for other people that come here from https://github.com/w3tecch/typeorm-seeding, this is out of date.

Please check the commits as the Readme is also out of date. Check this PR for something a bit more helpful. PR Readme