When it comes to application development:
As pointed out by @Lux in the comments, there is no need for certain dependencies after the build process.
The final output of the application is the build, which is meant to be the end product. Typically, you do not rely on another application but rather on a package or addon for functionality.
Regarding addons:
There is a suggestion to list all of the addon dependencies in an application's package.json
file. This helps avoid unintentionally adding unnecessary files to the build through addons.
Therefore, the recommended approach in Ember for managing dependencies is to keep your dependencies in the devDependencies
section and include the addon dependencies in the application's package.json
using default blueprints. This allows users to customize them as needed.