Matt Felten

I would second this. I've been doing a lot more Jekyll websites recently and have to check in the compiled site and have Dploy exclude everything but the build dir....

Including that in release notes, or even better, an example in the Readme of how to customize more of the internal components would be great. If I didn't look into...

I'm experiencing the same exact warning right now and, yes, also using a custom storybook location. Moving my storybook folder to `/.storybook` removes that warning.

I haven't. Does that work?

Let me know if there's anything I can do to help on this. I'm looking into making a specimen right now but if I can use my time making it...

I'm looking for this too. Just tested the current version of `node-sass` to see if it's updated in 4.11, but it's not yet. https://github.com/mattfelten/node-sass-index-test

Just looked into this more. Looks like libsass has the change required in 3.6, but that hasn't been released yet. Looks like we're waiting for 3.6 to be released first....

@petekp Could you walk through how you generated the typings for that? `tsc --declaration tokens.js` doesn't love that it's not a TS file.

Ah that's clever. I ended up registering a new `ts` format and then running `tsc` on it. ``` module.exports = theo => { theo.registerFormat( "ts", ` // Source: {{stem meta.file}}...

That’s what I would expect. That the output can be packaged and “just work” in typescript projects. I don’t think we would need actual `.ts` files