Remove Node option from Python template? about templates HOT 7 CLOSED

When these templates were in the old repo, they shared same docs with images. For having node handy, all the images have a reason similar to this this one 👇

Given JavaScript front-end web client code written for use in conjunction with a Python back-end often requires the use of Node.js-based utilities to build, this container also includes nvm so that you can easily install Node.js.

Looks like it was assumed that node is helpful with most of the platforms/runtimes. This is what I think from the docs & why I kept this option during migration.

@Chuxel / @bamurtaugh might know the real reason behind it.

from templates.

There are few other templates which provides Node options in the UX. I'll remove those from Templates 👍

from templates.

Is there a problem we're trying to resolve here? e.g., has someone complained (I might have missed it)?

To break it down:

1. Most use cases for the images at the time were to enable web and service development where node was used by tools to generate client-side content (e.g. via webpack) even if you weren't deploying that way. Having yarn and nvm there by default both enabled these common tools use cases.
2. Image build performance is always a focus and removing the need to install yarn and nvm helps here.
3. Features didn't exist at the time.

Certainly, we could remove it from the template while still building yarn and nvm into the base image. Might that be a good way to get the best of all worlds?

from templates.

We recently added a lightweight way to create a dev container from scratch without a local folder or repository and there the additional and somewhat redundant step stood out and was brought to my attention. The UI steps are:

• Pick the Python template.
• Decide if and which Node version you want.
• Pick any additional features (including Node).

Since Node (and many other potentially useful tools) are offered as features, it seems we can remove Node from the template options. Having Node as an option made sense before we had features. I haven't checked which of the other templates are doing the same, but we could look into simplifying these too.

from templates.

Yeah I think we can remove it from the template - but we can still leave it in the image is my PoV. Retains the original functionality that way.

from templates.

+1 to removing - I think removing it would set the right precedent for other templates, where we want users to build up with features as much as possible.

from templates.

Closing as fixed with #59 🚀

from templates.