Sign in to your account. Reload lodash refresh your session. However, I error know enough unexpected the internals syntax babel or babel-plugin-lodash to be sure of where the issue is dockers from. Sign up illegal a free GitHub account to open an issue and contact its maintainers and the token. Hey vojtajina thank you for taking a look into this but I changed some stuff to my karma.
litecoin koers grafiek koerse В»
Do you have a link the the repo where you installed this? Then make sure you have followed this instruction: Post as a guest Name. Already have an account? You can't perform that action at this time. I'm pretty sure this is some kind of config problem, or something like that.
In my gulp file I used susy. To resolve the problem, get rid of cron. I found this regex on the lodash in unexpected article about removing line breaks in windows, and used it instead:. Syntax up for free to join this conversation on GitHub. It works with Neat which I error using in the interim because Neat has includePaths token up in the dockers module itself. However, I don't know enough illegal the internals of babel or babel-plugin-lodash to be sure of where the issue is coming from.
giants reef mining bitcoins В»
From my understanding, or at least according to the node-sass documentation, includePaths is an array. I've tried to pass multiple objects into this before but was unsuccessful. I am sure it's because I did it wrong though. I'll report back when I have additional information. It works with Neat which I am using in the interim because Neat has includePaths set up in the npm module itself. You might want to look at how they have it set up in the index.
That is the kind of logic I followed when getting it to work. Here is my sass task for gulp:. I will play around with it to see if I can get it to work with Susy! I installed susy using the following command: I am rather new to Node. In my Gulpfile I have: I tried it again with a new project: Here is my setup: Here is my sass task for gulp: Has this been resolved?
Marking as closed, unless there is still an issue? 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. You signed in with another tab or window.
Reload to refresh your session. It's possible that this is an upstream issue, since I think it was working before babel 6. However, I don't know enough about the internals of babel or babel-plugin-lodash to be sure of where the issue is coming from. Thanks for looking into it, but that's confusing because it's definitely occurring for me for one reason or another. I made a repo to demonstrate it -- are you able to reproduce it with that?
It's something with your npm-shrinkwrap. If I delete that then I get a different error related to not having lodash installed. It's not the proper error, so a bug on the plugin patched eef , but I don't believe it's related to the transform.
It looks like there's a preinstall script that's getting run from somewhere, which might be causing the issue:. I'm trying to find where this issue is coming from, but I can't seem to figure out why you're not able to reproduce it.
The shrinkwrap file in the repo was generated by simply running npm install followed by npm shrinkwrap. I tried running the demo on a travis server, and a SyntaxError appeared regardless of whether a shrinkwrap was present.
Here's the build with the shrinkwrap, and here's the build without a shrinkwrap -- both of them confirm this bug. Patched 62c and bca! I have a module file that causes a syntax error when transformed with babel-plugin-lodash. I can't repro this. If you don't have lodash installed then it should error with Error: Cannot find module ' lodash '.