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 order to add Cypress component testing to a project, I need access to the webpack.config.js file. There is effectively no way to "eject" a React app generated using nwb (to use create-react-app terminology).
The FAQ tells you how to set the debug flag to view the generated Webpack configuration, but it renders the runtime representation (aka console.log) which contains things like [Function] and cannot be copied. It might be possible for me to re-create the Webpack config file by diving into the nwb codebase, but nwb should be able to simply write out the config file being used so it can be require()-d by other tools.
The text was updated successfully, but these errors were encountered:
Hi @alecmerdler! I'm facing the exact same problem 1.5 years after you.
Were you able to find an alternative way of hooking up Cypress component testing to nwb?
In order to add Cypress component testing to a project, I need access to the
webpack.config.js
file. There is effectively no way to "eject" a React app generated usingnwb
(to usecreate-react-app
terminology).The FAQ tells you how to set the debug flag to view the generated Webpack configuration, but it renders the runtime representation (aka
console.log
) which contains things like[Function]
and cannot be copied. It might be possible for me to re-create the Webpack config file by diving into thenwb
codebase, butnwb
should be able to simply write out the config file being used so it can berequire()
-d by other tools.The text was updated successfully, but these errors were encountered: