Closed mateuswetah closed 7 years ago
Double-check that you're running npm install
before building, and that the node_modules
folder actually contains angular2-masonry
.
If node_modules
is missing the folder, and npm install
isn't behaving how you're expecting it to, it might be the package-lock.json
file that's to blame.
Hi there. Wow, this was a long time ago xD
Although I ended up moving to another library due to a design decision, I should have posted here that I find out what was the problem. I was moving my code to server without updating node_modules folder, so obviously a npm install
was needed... pretty dumb of me :P
Anyways, thank you :)
Hi guys!
Thanks for all the work, it really attends to a big requirement on the project that I'm working right now! The problem is, it's doing fine on my localhost tests, but once I move it to server and try a
ng build
, I get this error:i installed it via
npm install angular2-masonry --save
, which works, now I have"angular2-materialize": "^6.7.1"
in my dependencies.And loaded in my
app.module
just as described in the docs:is there anything else that I'm missing? I did everything from the Readme, except for the System.js part, as I'm using Webpack.
My versions:
I'm sorry if it's a dumb question, I'm pretty new on Angular2 :P