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
I've started using the library to model a small state machine for a react app and I believe that when doing a production build of my app, the testStateMachine code is included in it. (I'm using webpack to build my app).
Can this be the case?
If it's not the case, sorry for the confusion. In case this is happening, is there a way to prevent this?
This is just a guess, but I think this happens because ./src/testStateMachine.js is required from ./src/index.js. Maybe this could be change to allow users to import it explicitly in the application code with something like
Thank you very much for opening this issue, @san650.
I confirm that testStateMachine is included in the bundle, and we are discussing possible solutions in #32.
Let me close this, in favour of the other one, and please feel free to contribute to the discussion.
Hi,
Thanks for the library, it's awesome!
I've started using the library to model a small state machine for a react app and I believe that when doing a production build of my app, the testStateMachine code is included in it. (I'm using webpack to build my app).
Can this be the case?
If it's not the case, sorry for the confusion. In case this is happening, is there a way to prevent this?
This is just a guess, but I think this happens because
./src/testStateMachine.js
is required from./src/index.js
. Maybe this could be change to allow users to import it explicitly in the application code with something likemaking the file optional for users, in my case, I want to include it only in dev/test builds.
Let me know if you would accept a PR for making this happen 😃 .
The text was updated successfully, but these errors were encountered: