npm packages no longer stored in repository

[Andrew Eisenberg]

We have recently removed the npm packages from the scripted git
repository. Now, after cloning scripted from github, you will need to
run `npm install` in order to grab the dependencies. We are also now
using bower for the client components. Bower will be installed
automatically by npm and then will be used to install the client
components.

[Marcel Rassinger]

I just tried to get the latest commit (e9ba5ea0f3) running but the browser couldn't load requirejs. Comparing the client\scripts\lib directories  of the latest commit with version 0.3.0 shows that the requirejs folder is missing.

I got the latest commit by using git clone and npm install. Both worked fine. However, did I do something wrong?

[Scott Andrews]

That's the intended behavior.

-Scott

Sent from my iPad

[Kris De Volder]

@Marcel,

Its not quite clear to me from the messages in this thread if your
problem actualy got resolved...

If you are still having issues with running scripted because of
missing dependencies (like requirejs).
Try a complete and thorough cleaning and re-installing of the
dependencies like so:

    cd scripted     # go stand at the root of your git clone
    git clean -fxd  # remove all files/dirs from the filesystem that are *not* in the repo
    npm install      # reinstall all external dependencies

I found I needed to do this kind of cleaning sometimes because
existing stuff in node_modules
confuses the npm install.

Now try again.

Let us know if you still have problems.

[Xavier Seignard]

Hi, I noticed you removed node_modules from version control.

I'm still wondering if it's a good practice. Here is an argumentation that speaks to me : http://www.futurealoof.com/posts/nodemodules-in-git.html

I can't make my own opinion on that subject, but I think it's a good read.

Keep on the good work, I really do like scripted, and i use it as my daily IDE

Regards

Xavier

On Tuesday, January 22, 2013 6:58:52 AM UTC+1, Andrew Eisenberg wrote: