You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use yarn start to observe a seemingly functional project
Use yarn build and serve -s build to observe a very broken project
Expected Behavior
I thought the built code would work, as the watched code did.
Actual Behavior
I get a cryptic react error. A cursory search reveals that this may lay in mismatched react versions, but I'm not sure how it can be that if the watched version works fine.
Error:
Uncaught TypeError: Cannot read property 'getStackAddendumByID' of undefined
at eval (webpack-internal:///28:4953)
at Object.eval (webpack-internal:///28:17220)
at eval (webpack-internal:///28:17223)
at Object.<anonymous> (index.js:265)
at e (index.js:21)
at Object.eval (webpack-internal:///24:37)
at eval (webpack-internal:///24:40)
at Object.<anonymous> (index.js:237)
at e (index.js:21)
at Object.eval (webpack-internal:///23:14)
If I look at the included react and react-dom in inspector, they both appear to be v16
Reproducible Demo
I'm trying to make an example for an NPM module I'm publishing. I'm not very well versed in this so it could be my fault but the fact that it works when using yarn start does raise some eyebrows so I thought I'd bring it up.
The text was updated successfully, but these errors were encountered:
fozzle
changed the title
App appears to work with start but not when built + serve
App appears to work with start but not with build + serveOct 23, 2017
fozzle
changed the title
App appears to work with start but not with build + serve
App works with start but not with build + serveOct 23, 2017
Is this a bug report?
Hm, sort of? Could very well be user error.
Can you also reproduce the problem with npm 4.x?
Symptoms are the same no matter Yarn, NPM4, or NPM5.
Which terms did you search for in User Guide?
Just looked over the build and deployment settings.
Environment
node -v
: 8.1.3npm -v
: 4.6.1yarn --version
(if you use Yarn): 1.0.1npm ls react-scripts
(if you haven’t ejected): 1.0.14Then, specify:
Steps to Reproduce
Basically, my project works if I use
yarn start
but not if Iyarn build
and thenserve -s build
(Write your steps here:)
yarn start
to observe a seemingly functional projectyarn build
andserve -s build
to observe a very broken projectExpected Behavior
I thought the built code would work, as the watched code did.
Actual Behavior
I get a cryptic react error. A cursory search reveals that this may lay in mismatched react versions, but I'm not sure how it can be that if the watched version works fine.
Error:
If I look at the included react and react-dom in inspector, they both appear to be v16
Reproducible Demo
I'm trying to make an example for an NPM module I'm publishing. I'm not very well versed in this so it could be my fault but the fact that it works when using
yarn start
does raise some eyebrows so I thought I'd bring it up.project github: https://github.com/fozzle/react-burrito-type-example
url of 'deployed code' with error: https://kpetrovi.ch/react-burrito-type-example
The text was updated successfully, but these errors were encountered: