Skip to content

ng install issues and proposals #236

Closed

Description

@xmlking

Issues

  1. shouldn't allow ng install *
  2. shouldn't create dist\node_modules
  3. ng install ng2-slimscroll corrupt my code

screen shot 2016-02-21 at 1 29 05 pm

### NPM upgrade requests 1. Angular: 2.0.0-beta.7 2. rxjs: 5.0.0-beta.2 3. typescript : next ### Proposals

when developer manually installed a lib via npm and add to vendorNpmFiles in ember-cli-build.js

    vendorNpmFiles: [
        'moment/moment.js'
    ]

automatically add to System.config in index.html

  paths: {
    'moment': 'vendor/moment/moment.js'
  }

Activity

  1. hansl commented on Feb 21, 2016

    @hansl
    Contributor

    We are well aware of issues with the third party installation and are in the process of formulating a better solution. The whole process is being thought out and we will carefully take this into consideration.

    As the thing will be likely ripped out and not used, I'll close this and suggest you wait for the new solution. You can for now install third parties from npm and manually add them to your build.

    Cheers.

  2. NathanWalker commented on Feb 23, 2016

    @NathanWalker
    Contributor

    It makes sense for the lib install tool to become a separate tool outside of angular-cli.

    @hansl Since the intent of the effort was community grown, we would appreciate some insight on what you guys are thinking on the new direction?

  3. hansl commented on Feb 29, 2016

    @hansl
    Contributor

    There's a design that's being discussed on; #255. This is still in design phase.

  4. NathanWalker commented on Feb 29, 2016

    @NathanWalker
    Contributor

    Thank you @hansl ! Really like the sounds of that even at the early stage 👍

  5. angular-automatic-lock-bot commented on Sep 5, 2019

    @angular-automatic-lock-bot

    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.

  6. locked and limited conversation to collaborators on Sep 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions