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
In relation to purescript-concur/purescript-concur-react#41, I've been wondering if react-devtools might provide some insight. It might be good to build this functionality into this starter project, so that one could do things like build a development or profiling build.
However, I've been unable to do this so far, and I'm guessing it is in relation to parcel, though I'm not sure - most react projects seem to use webpack, and all the devtools instructions I've seen have been for webpack. Whenever I go to the profiling tab of react dev tools on my parcel/concur project, I'm unable to profile. An alternative, if a development build is enabled, is to use the performance tab which is a standard feature of the browser.
I've tried setting NODE_ENV="development" parcel build ..., but this didn't appear to help in my case.
The text was updated successfully, but these errors were encountered:
In relation to purescript-concur/purescript-concur-react#41, I've been wondering if react-devtools might provide some insight. It might be good to build this functionality into this starter project, so that one could do things like build a development or profiling build.
However, I've been unable to do this so far, and I'm guessing it is in relation to
parcel
, though I'm not sure - most react projects seem to use webpack, and all the devtools instructions I've seen have been for webpack. Whenever I go to the profiling tab of react dev tools on my parcel/concur project, I'm unable to profile. An alternative, if a development build is enabled, is to use the performance tab which is a standard feature of the browser.I've tried setting
NODE_ENV="development" parcel build ...
, but this didn't appear to help in my case.The text was updated successfully, but these errors were encountered: