Már Örlygsson

...the config files don't have to be implicitly selected. If you provide a `stylusSupremacy.configFile` setting in VSCode/Atom/etc. then a single config can be shared between editors and npm scripts. Allowing...

> when Remix posts to a route, it looks for an action on that route. If you're on an index route, it will look at the parent layout for an...

Here this is mentioned in passing: https://remix.run/docs/en/v1/api/remix#form-action

I am using version `0.22.0` and I have pretty much the same problem as @AntonPilyak ```js { // ... input: { foo: 'src/lorem/foo.ts', bar: 'src/ipsum/bar.ts' }, output: { dir: 'dist',...

Moreover it seems like it creates declaration files for every .ts file it finds, not just the entry points. ``` dist/ lorem/ foo.d.ts ipsum/ utils/ bar-helper.d.ts bar.d.ts some_other_ts_file/ not_imported_by/ neither_foo_nor_bar/...

Since it is a definition for `dist/foo.js` I had assumed it would end up next to it - just like the source map file – i.e. in `dist/foo.d.ts`. Will TypeScript...

Ah, so this plugin doesn't really manage any part of the declaration-build process. It just fires up `tsc` to do its thing, irrelevant of Rollup's process? Still, if I'm only...

Thing is, I'm exporting a set of standalone modules (`import tool1 from 'myTools/tool1';` etc..) so there's no single entry point to use in `pkg.types`. Each definition file must reside next...

I'm making a collection of standalone utilities. The root-folder of the published/installed package contains all the built module files in a flat list. (I'm writing them in TS/ES6 in a...

...I've been playing with `tsc` on the commandline a bit now, and I think I see now the limitations you're dealing with. I noticed, however, that if you run tsc...