Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When init new mean project, javascript files can't defined in html #978

Closed
ugurgungezerler opened this issue Dec 23, 2014 · 11 comments

Comments

Projects
None yet
8 participants
@ugurgungezerler
Copy link

commented Dec 23, 2014

When init new mean project, javascript files can't defined in html or in aggregated.js

@wladiston

This comment has been minimized.

Copy link

commented Dec 23, 2014

Same problem here... I tried to downgrade the npm but not worked

@hugotown

This comment has been minimized.

Copy link

commented Dec 23, 2014

I have the same problem ...

I wonder, you have implemented some kind of releases of the "stable-version"? I want to prevent clone what is currently in the repository without testing whether it works? ...

@FlorianKoerner

This comment has been minimized.

Copy link

commented Dec 23, 2014

Same here

@liorkesos

This comment has been minimized.

Copy link
Member

commented Dec 23, 2014

I'll check.
We need to have mean init clone "0.4.2" and not "latest"

@liorkesos liorkesos closed this Dec 23, 2014

@liorkesos liorkesos reopened this Dec 23, 2014

@flamecoals

This comment has been minimized.

Copy link

commented Dec 23, 2014

+1

@flamecoals

This comment has been minimized.

Copy link

commented Dec 23, 2014

screen shot 2014-12-23 at 11 10 58 am

mean status:\

MacFeliz:fundoDSJ Felizardo$ mean status

    MEAN Status
    -----------

    MEAN VERSION: 0.4.2

    DB connection successful!

    MongoDB URI: mongodb://localhost/mean-dev

    checking meanio and global mean-cli versions

/usr/local/lib/node_modules/mean-cli/node_modules/npm/node_modules/read-installed/read-installed.js:362
  Object.keys(deps).forEach(function (d) {
         ^
TypeError: Object.keys called on non-object
    at Function.keys (native)
    at unmarkExtraneous (/usr/local/lib/node_modules/mean-cli/node_modules/npm/node_modules/read-installed/read-installed.js:362:10)
    at /usr/local/lib/node_modules/mean-cli/node_modules/npm/node_modules/read-installed/read-installed.js:137:5
    at next (/usr/local/lib/node_modules/mean-cli/node_modules/npm/node_modules/read-installed/read-installed.js:185:14)
    at /usr/local/lib/node_modules/mean-cli/node_modules/npm/node_modules/read-installed/read-installed.js:169:14
    at Object.oncomplete (evalmachine.<anonymous>:107:15)

@liorkesos liorkesos closed this in 3cb6e15 Dec 23, 2014

@liorkesos

This comment has been minimized.

Copy link
Member

commented Dec 23, 2014

basically to fix in this sitiation run
npm install assetmanager@1.1.1 .
Some change in assetmanager 1.1.2 is causing this. fixed by hardcoding package.json

@ugurgungezerler

This comment has been minimized.

Copy link
Author

commented Dec 23, 2014

thanks for solution 👍

@davecyen

This comment has been minimized.

Copy link

commented Dec 23, 2014

Thanks. I had the same issue and this resolved it.

@hugotown

This comment has been minimized.

Copy link

commented Dec 23, 2014

Thanks 👍
Solved!

liorkesos added a commit that referenced this issue Dec 23, 2014

hardcoded devDependencies
To avoid bugs like #978
@schapira

This comment has been minimized.

Copy link

commented Dec 24, 2014

now its work good for me, thanks.
play time :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.