npm dependencies are not getting resolved for dev environment

[mreferre]

npm dependencies are not getting resolved for dev environment

[mreferre]

Hi @munjalt. Thanks for your issue. I will admit I have defocused a bit from the localdevelopment deployment option because all the dependencies are very fragile (as you figured). I did have created a localtest deployment options that seems to be similar to what you are describing (which happens to be also similar to a docker compose deployment.

Is that enough for what you are trying to achieve? I am literally wondering if I should get rid completely of the localdevelopment deployment option to avoid confusion.

[munjalt]

@mreferre thanks for the quick response. I did end up using the localtest deployment option. I think that works for folks like me who just want to test out some code and who aren't savvy frontend devs. But someone who wants to play around could get stuck with the dependencies error. That's why I thought I should bring this to your notice.
But this was really helpful thank you so much!

[mreferre]

@munjalt yep I agree with you that the localtest is fine if you want to .. guess what... test it :) but not so much if you want to tweak it. Perhaps I should redo entirely the localdev approach by prescribing to use selected node and ruby images mounting the local folders (instead of demanding that your dev device has the right node and ruby environments installed). This way you could tweak the source code interactively and see what happens (for npm for sure, I don't know if ruby has a fast-reload option though). Thanks! I appreciated you bringing this up (it's something I have been thinking AND THEN PARKING for a long time).