-
Notifications
You must be signed in to change notification settings - Fork 70
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
Error from importjs#ImportJSImport
command
#1
Comments
On line 71 in Edit: Support for newlines after method calls was added in Ruby 1.9 so my Vim installation must be using an old version of Ruby. @trotzig Moving the placement of the dot makes this backwards compatible with old Ruby versions, like so:
However, this Ruby styleguide recommends keeping the dot as the prefix rather than placing it at the end like this. I agree that the 1.9 syntax is more readable. Options:
I'll submit pull requests for each option. |
It looks like you can use the commands Mine is using '1.8.7' which is probably just the system default. I'm going to try and set it to one of the more recent versions. |
Closed by 0cd733e |
The package.json file of a node module can (and often does) contain a `main` property pointing to the main module of a package. For instance, the package.json of the `json-sass` package points to "lib/jsonSass.js". To import json-sass, all you have to do is `require('json-sass')`. Webpack and other node-compatible tools will figure out what file to really look for based on the information in the package.json file. There's one side-effect of how I implemented this behavior that I hope to address soon: when multiple files resolve to a variable and one of them is derived from the package.json file, you will see something like this: [import-js]: Pick file to import for `Foo`: 1. Foo/package.json 2. bar/foo.js It would be better if #1 said "Foo", or perhaps the entire path to the Foo folder, "app/assets/components/Foo". I plan on tackling that later. Fixes #27
When I try to use 'importJS' I have been seeing this error:
I'm going to look into it a bit and see if I can find the problem. Since this does not happen on my work laptop, I assume it is related to something in how my environment is set up.
The text was updated successfully, but these errors were encountered: