Glen
Glen
Would it be possible to add support for building Sass files? https://esm.sh/vuetify@next > /* esm.sh - error */ throw new Error("[esm.sh] " + "esbuild: No loader is configured for \".sass\"...
This will make working with the hierarchical records a lot easier. Using getParent() (which creates a new query each time) is not ideal. Doctrine 1 has this.
Please refer to https://github.com/floridoo/gulp-sourcemaps/issues/124. I am experiencing exactly the same problem using the following Gulp task (ES2015): ``` js gulp.task("build-css", () => { return gulp.src(cssSrc) .pipe(newer({ dest: cssDest, ext: ".css"...
In this interface: ```ts export interface Schema { type: SchemaType; openApiVersion?: 2 | 3; id: SchemaId; content: JsonSchema; rootSchema?: Schema; } ``` ... `content` is typed as `JsonSchema`, but `JsonSchema`...
Adding a separate configuration file for every tool is not ideal, especially when there's not a lot of configuration. It would be nice to be able to configure this tool/plug-ins...
Tools like [openapi-typescript](https://github.com/drwpow/openapi-typescript) insert a header comment like: ```ts /** * This file was auto-generated by openapi-typescript. * Do not make direct changes to the file. */ ``` There may...
```php [ 'disabled_vendors' => ['jquery'] ] ``` Similar to using the `disableVendor` method, but via an option that allows multiple vendor names to be listed.
Is this package compatible with GraphQL v16? I see that it has a dev dependency on v15.
It only includes v2.0.0.
It's now possible to use CleanCSS: ```js const CleanCss = require("clean-css"); new OptimizeCssAssetsPlugin({ cssProcessor: CleanCss, cssProcessorOptions: { sourceMap: true } }) ``` ... but source maps do not work. [CleanCSS.process](https://github.com/jakubpawlowicz/clean-css/blob/887ac0e2d1f10e16663edf0719153f18597824d5/lib/clean.js#L51)...