-
Notifications
You must be signed in to change notification settings - Fork 22
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
Index.js is missing #12
Comments
This might be related to your old version of npm. Not sure why exactly or
how to fix it. I'll need to investigate.
…On 3 May 2017 4:16 am, "Gianpietro Lavado" ***@***.***> wrote:
Hi,
Not sure why, my environment has been pulling a scss-tokenizer version
without an index.js file, so I've had to manually generate it every time.
It's been called by saas-graph 2.1.1, which package.json file says:
""scss-tokenizer": "^0.2.1""
Details of my environment (I know it's kind of old, but it's an
application requirement):
- Ubuntu Trusty 14.04.4
- Node version 0.10.25
- NPM version 1.3.10
Regards,
Gianpietro
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#12>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAjZWJCuK45GK3-RaIAi73HqT1oC5ZxDks5r1-NygaJpZM4NO5PA>
.
|
Thanks for checking into this. I'm seeing a similar error with npm v0.10.38. This started within the past few days. We have sass-graph@2.2.2 which depends on scss-tokenizer@0.2.1. |
That's a node version not an npm version. Node 0.10 and npm 1 are end of
lifed so I'm not sure if there's anything we can do but I'll try to
reproduce it locally.
|
+1 |
1 similar comment
+1 |
Can you all please confirm your node and npm versions?
|
npm version 1.3.10 |
npm 1.4.28 |
I have not been able to reproduce this locally with
Could y'all please show the output of listing the files in
* the path may be different on your system. Also please try downloading the tarball directly and confirming the
The end of the output should how the tarball url dist:
{ shasum: '07c0cc577bb7ab4d08fd900185adbf4bc844141d',
tarball: 'https://registry.npmjs.org/scss-tokenizer/-/scss-tokenizer-0.2.1.tgz' }, |
Also I would like to add a remark, even when I |
Thanks @rasta-rocket, this is fascinating. |
Ok I've been able to reproduce this with
After some npm version bisecting I have been able to reproduce this issue up until npm@1.4.0 but not after. This conflicts with the information provided by @jfridye. I'm going to investigate some potential workarounds |
This shouldn't be necessary but may resolve an issue with npm@<1.4.0. See #12.
I believe this is resolved in v0.2.3. Please confirm. |
Also I tested the 0.2.0 version, the index.js is present |
Fixed in d84958c |
Thx. Do you will update the new version on sass-graph package.json ? |
Published sass-graph@2.2.3 |
Hi,
Not sure why, my environment has been pulling a scss-tokenizer version without an index.js file, so I've had to manually generate it every time.
It's been called by saas-graph 2.1.1, which package.json file says: ""scss-tokenizer": "^0.2.1""
Details of my environment (I know it's kind of old, but it's an application requirement):
Regards,
Gianpietro
The text was updated successfully, but these errors were encountered: