codesandbox / codesandbox/codesandbox-client

React production build fails while development works

Open
#6,489 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
13.6k
Forks
2.4k
Avg merge
6d 19h
Merged PRs (30d)
2

Description

🐛 bug report

Description of the problem

My same piece of code works with codesandbox environment, but the production build on Netlify is throwing errors.

How has this issue affected you? What are you trying to accomplish?

I'm trying to create a production build with codesandbox.

To Reproduce

You can change the dependencies version in package.json to get more errors like duplicate bitcore lib, etc.

Link to sandbox:

https://codesandbox.io/s/working-o1hfrh?file=/package.json

Link to build:

https://csb-o1hfrh.netlify.app/

Check console for error log.

Your Environment
Software Name/Version
Сodesandbox c93f76ef3
Browser Chrome Version 98
Operating System Windows 10

Preflight Checklist

  • I have read the Contributing Guidelines for this project.
  • I agree to follow the Code of Conduct that this project
    adheres to.
  • I have searched the issue tracker for an issue that matches the one I want
    to file, without success.

Contributor guide

Open the contributing guide

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 the linked CodeSandbox package.json and compare the development setup with the Netlify production build, then inspect the console error on the linked deployment. Check the dependency versions and the reported duplicate bitcore library errors. Done means the same project produces a working production build without the reported errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
build-system, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.