Build fails with Scheme = release

Open
#14 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
react-native

Research direction

Start with the release build configuration and the Metro transform/minification path shown in the stack trace; inspect how ../../node_modules/@toruslabs/torus-embed/dist/torus.cjs.js is handled. Done means a release build completes without the reported Unexpected token error, with a regression check if the repository has one.

Written by the indexing model from the issue text.

Description

Getting this error after updating when trying to build for release mode:

error ../../node_modules/@toruslabs/torus-embed/dist/torus.cjs.js: Unexpected token name «_000», expected punc «,» in file ../../node_modules/@toruslabs/torus-embed/dist/torus.cjs.js at 129:23.
Error: Unexpected token name «_000», expected punc «,» in file ../../node_modules/@toruslabs/torus-embed/dist/torus.cjs.js at 129:23
    at minifyCode (/Users/billy/Programming-LOCAL/frontend/apps/react-native/node_modules/metro-transform-worker/src/index.js:99:13)
    at transformJS (/Users/billy/Programming-LOCAL/frontend/apps/react-native/node_modules/metro-transform-worker/src/index.js:320:28)
    at transformJSWithBabel (/Users/billy/Programming-LOCAL/frontend/apps/react-native/node_modules/metro-transform-worker/src/index.js:411:16)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Object.transform (/Users/billy/Programming-LOCAL/frontend/apps/react-native/node_modules/metro-transform-worker/src/index.js:572:12)
Dominant language
TypeScript
Stars
7
Forks
4
PR merge metrics
No merged PRs in 30d

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.

More from MetaMask/react-native-web-browser

All issues in MetaMask/react-native-web-browser

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.