Repository navigation
fix(install): ng install should not require bundles #189
Description
I couldn't find an issue for this already, but I think there's already a goal for the install process to not require bundles to be included in the installed package. Ideally the main file from a package.json could be used as an entry point to grab the lib's modules and include them in build artifacts.
Activity
jkuri commentedon Feb 11, 2016
Is this possible?
node_modulesdirectory is not accessible from thedist/dir.jkuri commentedon Feb 11, 2016
Also, bundles will not be needed anymore as of TS 1.8.
Edit: sorry, the bundler script will not be needed anymore, bundles would be generated without
systemjs-builder.jeffbcross commentedon Feb 11, 2016
I meant that the process that currently builds/moves files to
distshould be able to move the correct files fromnode_modules/some_packagetodist/some_package, or bring the required files into the app bundle using systemjs-builder.jkuri commentedon Feb 11, 2016
Okay, that makes sense.
hansl commentedon Mar 1, 2016
We removed the
installfeature temporarily, while working on a design doc. So closing this.angular-automatic-lock-bot commentedon Sep 5, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.