-
Notifications
You must be signed in to change notification settings - Fork 4
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
Wrong result of import after updating modules
to 0.9.0
#33
Comments
I think you're right. I haven't been maintaining this plugin for a long time now, so, it is bound to have issues. I would suggest using the ecmascript package instead, because the main real benefit from using my package was the integration with ng-annotate. When I was still coding in angularjs I was using my ng2now library, available on npm, which largely removes the need for using ng-annotate and allows you to write code that looks like angular2. Sorry I can't give you better news. |
I've now solved it differently - you could also update your README.md if you want ... Since this package doesn't seem to be maintained anymore, and running For anyone running into this, run the following commands:
And add the following lines to your
It seems that Meteor ignores the file I also want to encourage you to provide this as a drop-in replacement, since it is 😉 No drawbacks so far. |
Thanks @SimonSimCity! I first had to remove all dependencies to |
It's not working for me after all 😢 package |
Found a solution! According to EDIT : my codemod for including angular import when needed :
(then replace all |
@aymericbouzy Yes, that's exactly what I was going to suggest :) I'm glad you found it! |
Thanks : now I run into another issue :
Is it because I'm running Meteor 1.3.5.1 (Node 0.10.x ?) My issue is that I can't upgrade to Meteor 1.5 for now, but I still want to be able to use es6 syntax, especially modules. This project I have to maintain has so many outdated dependencies 😵 |
@aymericbouzy wasn't ES2015 support actually introduced in Meteor |
@aymericbouzy Can you share your repo? I will try to help you. |
Hi,
$ meteor npm install --save-dev babel-plugin-angularjs-annotate npm ERR! Failed to parse json NPM Log:0 info it worked if it ends with ok Can you direct me, to resolve. As I have completed the development few months back, hoping to replace minimum workable solution. Thanks |
@ananthavel could you please post your package.json here? I think it may be missing a comma. |
"name": "proj-name", |
@ananthavel add a comma just before the "babel" key |
Thanks pbastowski, it solved my problem. |
Hi pbastowski, Error Unable to resolve some modules: “cordova/exec” in /home/ananth/workspace-meteor/proj-name/android/android/project/platform_www/cordova-js-src/platform.js If you notice problems related to these missing modules, consider running: meteor npm install --save cordova W20170919-22:44:33.561(5.5)? (STDERR) /home/ananth/workspace-meteor/proj-name/android/android/project/cordova/node_modules/plist/examples/browser/index.html:1 Can you suggest me any idea? Regards, |
If you read the error, it says :
Also, first copy paste your error on Google and try solving by yourself before asking for help.
|
@aymericbouzy the @SimonSimCity amazing work, bud. It truly is a seamless drop-in, and I'm so happy to have all the latest |
I have no knowledge at all of AngularJS, and I don't wish to start learning. The project I'm in charge of is simply in maintenance mode while we figure out how to rebuild a better solution. |
I guess your extension here is incompatible with
modules
since v0.9.0. It's quite easy to reproduce. Here's a quick manual of how to do it. Install a plugin (likehwillson:stub-collections
) into a fresh project (like described here: hwillson/meteor-stub-collections#17 (comment)). Run the project by callingmeteor
and you see, that it works as expected. In your console you see that the import returnsIt also returns this result after replacing
ecmascript
by your plugin whilemodules
is on v0.8.2 or lower. But after updating this module the result changes into:If I now replace your plugin back with
ecmascript
while leavingmodules
in a version like v0.9.0 I get the expected first result again.I suppose, this has something to do with your plugin being incompatible with the latest changes of the
modules
package ... or am I mistaken here?The text was updated successfully, but these errors were encountered: