Current Stylus Version is not working
28Bytes opened this issue · comments
I have downloaded the current master zip file and placed the files into my project and when compiling most functions are not working. Columns are not working etc the only thing I can get working is edit() any ideas? Is there a bug in the current stylus version?
Same here.
Looks like the aliases are not working properly.
Could you try using the functions with a j-
prefix? So you are calling them directly and not the alias function, maybe that will solve the problem (and help me find the issue what's actually wrong)
Yes that worked. Just remove all the j- instead of having the aliases.
So in the grid.styl would be "column" not j-column etc for all of them...
Might even want to change the "j-cf" to just "clear" vs "cf" just reads better in your stylus file.
@rodrigobr92 @28Bytes could both of you try the current master again?
I just updated (or more accurately reverted) an alias change and now the aliases should be working properly.
Working perfectly with gulp-stylus
using jeet from master
. When is a new release planned?
@28Bytes Please try again using 6.1.5
, I just now went ahead and reverted the codebase back to 6.1.2 and re-released the old working code (just to have clean progress)
everything should be working as expected again.
Default aliases are completely removed in 7.0.0.
6.1.5 is working, 7.0.0 gives the same "failed to locate jeet.styl".
@Krajsnick Did you follow the migration guide? Can you send your config?
Try simply removing the @import
statement.
@corysimmons Using it with Express 4:
app.use(stylus.middleware({
src: path.join(__dirname, 'views'),
dest: path.join(__dirname, 'public'),
compile: function(str, path) {
return stylus(str)
.set('filename', path)
.use(require('jeet')())
.use(require('rupture')())
.import('jeet')
}
}));
I have tried without the .import('jeet')
but it still doesn't work, cannot locate jeet.styl
. What would be the correct import path?
@corysimmons It was working the whole time, it was my col()
that was not working anymore, didn't read careful enough in the migration guide - sorry.
@Krajsnick No problem! I'm glad it's working. When you said it couldn't locate jeet.styl
I knew something was fishy because 7.0.0 doesn't have a jeet.styl
referenced anywhere anymore. :D