ERROR in LockerModule is not an NgModule about angular-safeguard HOT 29 CLOSED

Unfortunately no - @MikaAK if you want to drop support for this package, please let us know so we can all move on. Just please don't keep us all in the dark? Thanks!

from angular-safeguard.

Hi Mika,

Sorry for the late reply! Stupid question; How do I go about using the master branche? Just using angular-safeguard@latest?

Thanks again

from angular-safeguard.

Probably related to #24, you can try using master, tests need to be updated then i can publish

from angular-safeguard.

ERROR in Error encountered resolving symbol values statically. Calling function
'LockerModule', function calls are not supported. Consider replacing the functio
n or lambda with a reference to an exported function, resolving symbol AppModule

from angular-safeguard.

I'm having the same issue as @txone now. @MikaAK can we try and figure out what is going wrong here together? 😄

Thanks!

from angular-safeguard.

you would have to go into package.json and point to angular-safeguard: "mikaak/angular-safeguard" I haven't had time to fix tests but as soon as it's done I'll release :(

from angular-safeguard.

@MikaAK I just tried setting "angular-safeguard": "mikaak/angular-safeguard" in my package.json and then running npm update but that results in a Module not found: Error: Can't resolve 'angular-safeguard' error.

I'm probably doing something wrong here.. But the fact that AoT compilation doesn't work is a real issue here. 😞

Thanks anyways!

from angular-safeguard.

@Octopixell "angular-safeguard": "git://github.com/mikaak/angular-safeguard.git
From NPM docs

from angular-safeguard.

@Octopixell are you using yarn? I ran into someone who was getting these messages when using yarn to install, but not when using npm

from angular-safeguard.

@MikaAK nope we're using NPM for all our packages.

from angular-safeguard.

Ok good to know, was just something I heard of but I'll look into this more. I've been working at 3 jobs currently as such no time to do anything. One of them ends in a month however so I should get a chance to take a look then. Or if i get any spare time this is next on my list

from angular-safeguard.

@MikaAK I suppose I could use master if that's stable at the moment :)

from angular-safeguard.

@MikaAK so what is the progress in solving AoT with this module? Latest version from npm (1.0.1) doesn't work with AoT.

I am not able to download this npm package from github in any syntax.

Can you please post full package.json row that works for you?

Thank you!

from angular-safeguard.

@MikaAK using "angular-safeguard": "git://github.com/mikaak/angular-safeguard.git" in my package.json does not actually fix anything. It actually just breaks things that much more. Check the following error:

ERROR in ./src/app/services/apps.service.ts
Module not found: Error: Can't resolve 'angular-safeguard' in '/Users/marco/dashboard/src/app/services'
 @ ./src/app/services/apps.service.ts 12:0-43
 @ ./src/app/apps/apps.component.ts
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi webpack-dev-server/client?http://0.0.0.0:4200/ ./src/main.ts

from angular-safeguard.

Just realised that this happens because the module isn't being built since it's not installed by NPM(?). Maybe I'm wrong though.. In any case, I'm getting into some serious trouble now since I was supposed to launch today.

from angular-safeguard.

Building the module by hand results in the following:

Marcos-MacBook-Pro:angular-safeguard marco$ npm run build

> [email protected] build /Users/marco/dashboard/node_modules/angular-safeguard
> NODE_ENV='production' webpack --progress && rm -rf ./dist/test

Hash: 50b55294f53c015f869e             
Version: webpack 2.3.3
Time: 986ms

ERROR in Could not resolve "/Users/marco/dashboard/node_modules/angular-safeguard/src/Locker.module.ts" from "/Users/marco/dashboard/node_modules/angular-safeguard/src/Locker.module.ts".

ERROR in Entry module not found: Error: Can't resolve './src/index.ts' in '/Users/marco/dashboard/node_modules/angular-safeguard'

npm ERR! Darwin 15.5.0
npm ERR! argv "/Users/marco/.nvm/versions/node/v6.9.4/bin/node" "/Users/marco/.nvm/versions/node/v6.9.4/bin/npm" "run" "build"
npm ERR! node v6.9.4
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! [email protected] build: `NODE_ENV='production' webpack --progress && rm -rf ./dist/test`
npm ERR! Exit status 2
npm ERR! 
npm ERR! Failed at the [email protected] build script 'NODE_ENV='production' webpack --progress && rm -rf ./dist/test'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the angular-safeguard package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     NODE_ENV='production' webpack --progress && rm -rf ./dist/test
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs angular-safeguard
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls angular-safeguard
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/marco/dashboard/node_modules/angular-safeguard/npm-debug.log

Is master really up to date? Or do you still have local changes?

from angular-safeguard.

This error is still present. I have tried building from master branch too. When is the release expected ?

from angular-safeguard.

Unfortunately, it seems not very soon. Mika however said this would be the case in this comment: #29 (comment)

I have already switched over to another package as I had to launch the app before a certain deadline. Not so happy about that as I'd rather have used angular-safeguard. My knowledge of making modules and packages for Angular2 isn't good enough, otherwise I'd have done a pull request or something similar.

from angular-safeguard.

Thanks for the replay Octopixell. I'm in a similar situation. May I know what package you have used.

from angular-safeguard.

@maytis In order to launch our app we had to resort to this package: https://www.npmjs.com/package/angular2-cool-storage

from angular-safeguard.

sorry guys, I've had a contract that's been really pressing on top of my regular job so I've had no personal time. It's due this weekend so I'll have some time afterwords :)

from angular-safeguard.

Hey @MikaAK have you gotten the chance to get into this now? I'm starting a new project right now and would love to use your module over any other stuff. Thanks!

from angular-safeguard.

This issue is a blocker & is pending from Feb on.

@MikaAK Why don't you release the module without the test cases?

You can work on them when you get time rather than letting this issue affect everyone who is using this module

from angular-safeguard.

Hi @MikaAK,

any news on this issue? It's also blocking me (I also tried using the master branch without success).

from angular-safeguard.

Same issue here.. Any fixes by now? 📦

from angular-safeguard.

I have also moved to
https://www.npmjs.com/package/angular2-cool-storage

At least for now,

from angular-safeguard.

guys I've lost hopes in this project...probably better to stop waiting and help building other projects that are actually maintained...

from angular-safeguard.

@demetrio812 how bout some PR's instead of that sass eh? I'm working 3 jobs right now and have no time for this. I have stated if someone can do a pr I will do support. Once 2 if my jobs end ill do it myself however

from angular-safeguard.

@MikaAK what ppl asked was a reply, just talking sometimes really help building a community around a project, some ppl already asked to support the project given that you don't have the time...

However, if I will need it and don't find something better, I'll do it, but the fact that you don't even have time to answer (or just to do a temp release) will also mean you may not even the time to review a PR

I understand it's not easy to maintain it while you have to prioritise work, but I can see from this conversation that many ppl are willing to help, if they are allowed to

from angular-safeguard.