uiwjs / uiwjs/react-md-editor

Unable to run the jest test

Open
#495 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2.9k
Forks
201
Avg merge
12m
Merged PRs (30d)
1

Description

Facing an issue while running the jest test in next.js

image

// jest.config.js
const nextJest = require('next/jest');

const createJestConfig = nextJest({
    // Provide the path to your Next.js app to load next.config.js and .env files in your test environment
    dir: './',
});

// Add any custom config to be passed to Jest
/** @type {import('jest').Config} */
const customJestConfig = {
    // Add more setup options before each test is run
    setupFilesAfterEnv: ['<rootDir>/jest.setup.js'],
    // if using TypeScript with a baseUrl set to the root directory then you need the below for alias' to work
    moduleDirectories: ['node_modules', '<rootDir>/', 'utils'],
    moduleNameMapper: {
        // Handle module aliases (This will be automatically configured for you soon)
        ...
        '@uiw/react-md-editor': '<rootDir>/node_modules/@uiw/react-md-editor/lib/index.js',
        'react-markdown': '<rootDir>/node_modules/react-markdown/react-markdown.min.js',
        rehype: '<rootDir>/node_modules/rehype/index.js',
        unified: '<rootDir>/node_modules/unified/index.js',
    },
    testEnvironment: 'jest-environment-jsdom',
    preset: 'ts-jest',
    transform: {
        '^.+\\.(ts|tsx)?$': 'ts-jest',
        '^.+\\.(js|jsx)$': 'babel-jest',
    },
};

 module.exports = async () => ({
     ...(await createJestConfig(customJestConfig)()),
     transformIgnorePatterns: ['node_modules/(?!(monaco-editor)/)', '^.+\\.module\\.(css|sass|scss)$'],
 });

module.exports = jestConfig;

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with jest.config.js and the referenced jest.setup.js, then reproduce the reported test failure in the Next.js application. The issue does not include the command or error details, so first identify the configuration error; done means the Jest tests run successfully with the intended setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
next.js, react, typescript
Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.