Open andykais opened 5 years ago
let me know if you prefer a repo to reproduce the problem, Im happy to make one!
@andykais I'm not sure I understand. Would you be willing to chat in a gitter room about this issue?
@andykais I have created gitter room for mochapack
here:
https://gitter.im/sysgears/mochapack
Thank you @andykais for raising this issue and having a chat about it. As per our chat conversation, it seems like a good idea to enable writing output to disk with some mochapack
cli flag, so that we support both in-memory output mode and filesystem output mode. The relevant Pull Request for original mocha-webpack
that can be of help to add back filesystem output support can be seen here:
https://github.com/zinserjan/mocha-webpack/pull/83/files
Hi, thank you for maintaining this fork! I have a project that creates child processes from other webpack entrypoints. Minimally reproducible example:
Running the tests with mochapack (or mocha-webpack) will fail because a fork (or any code that expects a physical file to work with from an entrypoint) cannot use the entrypoint.
What is the course of action here? Is there a simple workaround? If not, this is a feature request that proposes actually writing code to the build folder, which is not something mochapack/mocha-webpack has done in the past