question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Errors when attempting to build [Could be my fault]

See original GitHub issue

Working with the antd example, which is working in development it seems, but when I tried to build it I got the following error:

=> Copying public directory...
=> [✓] Public directory copied: 107.163ms
=> Building Routes...
=> [✓] Routes Built: 154.821ms
=> Bundling App...
Version: webpack 3.10.0
Time: 105ms

ERROR in Entry module not found: Error: Can't resolve 'ts-loader' in 'C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\lib\node_modules'

                => There were ERRORS during the prod build stage! :(
                => Fix them and try again!

Version: webpack 3.10.0
Time: 89ms

ERROR in Entry module not found: Error: Can't resolve 'ts-loader' in 'C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\lib\node_modules'

                => There were ERRORS during the node build stage! :(
                => Fix them and try again!

=> [✓] App Bundled: 5128.856ms
=> Exporting Routes...
TypeError: Cannot read property 'split' of undefined
    at _callee4$ (C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\lib\static.js:138:30)
    at tryCatch (C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\node_modules\regenerator-runtime\runtime.js:62:40)
    at Generator.invoke [as _invoke] (C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\node_modules\regenerator-runtime\runtime.js:296:22)
    at Generator.prototype.(anonymous function) [as next] (C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\node_modules\regenerator-runtime\runtime.js:114:21)
    at step (C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\lib\static.js:120:191)
    at C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\lib\static.js:120:437
    at Promise (<anonymous>)
    at C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\lib\static.js:120:99
    at exportRoutes (C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\lib\static.js:487:17)
    at _callee$ (C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\lib\commands\build.js:90:45)
    at tryCatch (C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\node_modules\regenerator-runtime\runtime.js:62:40)
    at Generator.invoke [as _invoke] (C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\node_modules\regenerator-runtime\runtime.js:296:22)
    at Generator.prototype.(anonymous function) [as next] (C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\node_modules\regenerator-runtime\runtime.js:114:21)
    at step (C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\lib\commands\build.js:27:191)
    at C:\Users\surface\AppData\Roaming\npm\node_modules\react-static\lib\commands\build.js:27:361
    at <anonymous>

I hope I didn’t do anything to break the setup. I don’t use typescript, so I changed some of the files from .tsx to .js in my project files (e.g., App.tsx). What might I be doing wrong?

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:8 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
loganpowellcommented, Jan 6, 2018

So, this is F’ing crazy showing up on HN… I think this what happened 😄


seldo 8 minutes ago [-]Hi folks, npm COO here. This was an operational issue that we worked to correct. All packages are now restored:https://status.npmjs.org/incidents/41zfb8qpvrdjreply | seldo 8 minutes ago [-]Hi folks, npm COO here. This was an operational issue that we worked to correct. All packages are now restored:https://status.npmjs.org/incidents/41zfb8qpvrdjreply
-- | --
seldo 8 minutes ago [-]
Hi folks, npm COO here. This was an operational issue that we worked to correct. All packages are now restored:https://status.npmjs.org/incidents/41zfb8qpvrdjreply
xwvvvvwx

I got the biblical echo that’s at the top of the thread as well.

0reactions
loganpowellcommented, Jan 6, 2018

If you want to see the most epic Github issue ever:

https://github.com/npm/registry/issues/255

Read more comments on GitHub >

github_iconTop Results From Across the Web

3 Things You can Do to Minimize Fault Cause by Human Errors
Faults usually happen when something is not working as the specs. Most defects cannot be prevented but avoided. The key to dealing with...
Read more >
Getting a segmentation fault when trying to build my GCC ...
1 Answer 1 · xgcc is located in $builddir/gcc . · xgcc -v ... will print the sub-commands it is calling, record the...
Read more >
Xcode build error after changing project target iOS major ...
I now get an error "The compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct...
Read more >
Common Build Problems
My build fails unexpectedly # ... One possible cause for builds failing unexpectedly can be calling set -e (also known as set errexit...
Read more >
Who Pays for Architect's Mistake?
The short answer is that the architect is responsible for clear-cut errors, but it is not always clear who is at fault. Sometimes...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found