meteor-scss: meteor 1.7 _includePaths is not iterable when importing scss file from node_modules

  • Feature request
  • Bug report
  • Question

meteor version: 1.7-rc.11

fourseven:scss version: 4.9.0

I added a symlink to my node_module in /imports and when i start meteor, i get the error

_includePaths is not iterable

EDIT: I added

{
  "includePaths": []
}

but now i get /client/main.scss: Scss compiler error: Error: File to import: {}/node_modules/mynodemodule/src/_file.scss not found in file:

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 9
  • Comments: 31 (4 by maintainers)

Most upvoted comments

I can confirm that this is a reload-related issue. Stopping and restaring Meteor solves the problem.

If you come here by Googling for “_includePaths is not iterable”: This appears to be a reload-related issue. Stopping and restarting Meteor helped in our hacking session today — Give it a try.

1.7.0.5 still happens

@tr4g Have you ever worked professionally as a software developer? Doesn’t sound like it, since you’d understand the compromise that is software development. Every software has bugs that affect only a subset of users and are therefore deemed too low priority to fix in the available time. In the meantime this works fine for the 99% of folks not experiencing this bug. That’s true for any software at every company.

So yeah, free doesn’t need to equal crap, but free surely means we don’t need to listen to your crap.

Same issue here. Meteor v1.8.0.2

@tr4g this is a third party, open source piece of software. Someone created it and generously put it into the world and allowed you to use it ,FOR FREE, in the hopes would save you time and effort. It is currently being maintained by members of the community who generously devote their time to help keep it, and numerous other packages, updated and available to you, FOR FREE. If you would like to join our efforts, by providing a viable minimal reproduciton, or even better a PR that fixes the issue, I’m more than happy to move things in the right direction. If however all you have to contribute are complaints and criticism, then I honestly wish you the best in your journey to firebase.

I also had the problem of “_includePaths is not iterable” for the following packages.

node_modules/ag-grid-community
node_modules/bootstrap        
node_modules/@owczar/dashboard-style--airframe 
node_modules/font-awesome
node_modules/rc-slider   
node_modules/react-big-calendar  
node_modules/react-bootstrap-table-next 
node_modules/react-bootstrap-typeahead 
node_modules/react-datepicker         
node_modules/react-grid-layout 
node_modules/react-image-crop 
node_modules/react-quill     
node_modules/react-toastify 
node_modules/react-toggle

What I did is as follows to fix it. In the root of your app:

mkdir packages
cd packages
git clone https://github.com/sebastian-ruiz/meteor-scss

This is a fork of meteor-scss I wrote that fixes this issue.

For react-toastify I still had problems and I had to do:

In imports/ui/packages/react-toastify/scss/main.scss make the following change:

@import "{}/node_modules/react-toastify/scss/_variables.scss"; 
// @import "variables";

I haven’t worked with meteor in a year and I didn’t do a pull-request for this change yet. I will do some more checks and then do a pull-request.

@copleykj you opensource kids always complain about people criticizing your products, like free has to equal crap, and that you only get quality when you pay.

3 years to fix a problem that needs a hacky workaround like symlinks, to do something expected to just work, is nonsense

but sure, it’s free

I ended up symlinking the folders from node_modules to import.

As per https://github.com/meteor/meteor/pull/9917 , the symlink method was reverted and going to be released as 1.7.0.1. Therefore closing this one.