Repository navigation
Replies: 2 comments 1 reply
|
This certainly seems like an emerging development approach (along with cloud-based dev), so it's intriguing. I've worked with a couple students who have older machines. They seem to be right at the edge of their machine's capabilities. It's certainly possible that docker development could be lighter weight, I suspect it is not. I'd want to make sure it doesn't make it any slower for folks. I'd also be concerned that this might would involve even more custom scripts to make things work. These are convenient, but take students away from the core tools and their documentation. Can we specify exact versions of node and npm in package.json? |
|
After more thought on this. I don't think this is worth doing as it'll deviate from standard workflows when working with Node. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Docker filesystem performance seems to be much better now on macOS, using it for Node development definitely feels possible again.
This would eliminate the issue of people using different versions of Node and npm, or just weird environmental issues in general, but would introduce its own pitfalls such as having to be inside the container in order to add packages to the project.
All reactions