@rindo/core 3.0.1 → 3.1.0

package/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rindo/core/cli",
-  "version": "3.0.1",
+  "version": "3.1.0",
   "description": "Rindo CLI.",
   "main": "./index.cjs",
   "module": "./index.js",

package/compiler/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rindo/core/compiler",
-  "version": "3.0.1",
+  "version": "3.1.0",
   "description": "Rindo Compiler.",
   "main": "./rindo.js",
   "types": "./rindo.d.ts",

package/compiler/rindo.d.ts

@@ -1,73 +1,73 @@
-import { Compiler, CompilerBuildResults, CompilerSystem, CompilerWatcher, CompileScriptMinifyOptions, Config, Diagnostic, LoadConfigInit, LoadConfigResults, OptimizeCssInput, OptimizeCssOutput, OptimizeJsInput, OptimizeJsOutput, PlatformPath, PrerenderResults, PrerenderStartOptions, TranspileOptions, TranspileResults } from '../internal/index';
-export { transpile, transpileSync } from './transpile';
-/**
- * The compiler is the utility that brings together many tools to build optimized components,
- * such as a transpiler, bundler, and minifier, along with many internal optimizations to
- * create small efficient compoennts. When using the CLI, the `rindo build` command uses
- * the compiler for the various builds, such as a production build, or watch mode during
- * development. If only one file should be transformed then the `transpile()` function
- * should be used instead.
- *
- * Given a Rindo config, this method asynchronously returns a `Compiler` instance. The
- * config provided should already be created using the `loadConfig({...})` method.
- */
-export declare const createCompiler: (config: Config) => Promise<Compiler>;
-export declare const createPrerenderer: (config: Config) => Promise<{
-    start: (opts: PrerenderStartOptions) => Promise<PrerenderResults>;
-}>;
-/**
- * The compiler uses a `CompilerSystem` instance to access any file system reads and writes.
- * When used from the CLI, the CLI will provide its own system based on NodeJS. This method
- * provide a compiler system is in-memory only and independent of any platform.
- */
-export declare const createSystem: () => CompilerSystem;
-/**
- * The `dependencies` array is only informational and provided to state which versions of
- * dependencies the compiler was built and works with. For example, the version of TypeScript,
- * Rollup and Terser used for this version of Rindo are listed here.
- */
-export declare const dependencies: CompilerDependency[];
-export interface CompilerDependency {
-    name: string;
-    version: string;
-    main: string;
-    resources?: string[];
-}
-/**
- * The `loadConfig(init)` method is used to take raw config information and transform it into a
- * usable config object for the compiler and dev-server. The `init` argument should be given
- * an already created system and logger which can also be used by the compiler.
- */
-export declare const loadConfig: (init?: LoadConfigInit) => Promise<LoadConfigResults>;
-/**
- * Utility function used by the compiler to optimize CSS.
- */
-export declare const optimizeCss: (cssInput?: OptimizeCssInput) => Promise<OptimizeCssOutput>;
-/**
- * Utility function used by the compiler to optimize JavaScript. Knowing the JavaScript target
- * will further apply minification optimizations beyond usual minification.
- */
-export declare const optimizeJs: (jsInput?: OptimizeJsInput) => Promise<OptimizeJsOutput>;
-/**
- * Utility of the `path` API providied by NodeJS, but capable of running in any environment.
- */
-export declare const path: PlatformPath;
-/**
- * Current version of `@rindo/core`.
- */
-export declare const version: string;
-export declare const versions: {
-    rindo: string;
-    typescript: string;
-    rollup: string;
-    terser: string;
-};
-/**
- * Current version's emoji :)
- */
-export declare const vermoji: string;
-/**
- * Compiler's unique build ID.
- */
-export declare const buildId: string;
-export { Compiler, CompilerBuildResults, CompilerSystem, CompilerWatcher, CompileScriptMinifyOptions, Config, Diagnostic, LoadConfigInit, LoadConfigResults, OptimizeCssInput, OptimizeCssOutput, OptimizeJsInput, OptimizeJsOutput, TranspileOptions, TranspileResults, };
+import { Compiler, CompilerBuildResults, CompilerSystem, CompilerWatcher, CompileScriptMinifyOptions, Config, Diagnostic, LoadConfigInit, LoadConfigResults, OptimizeCssInput, OptimizeCssOutput, OptimizeJsInput, OptimizeJsOutput, PlatformPath, PrerenderResults, PrerenderStartOptions, TranspileOptions, TranspileResults } from '../internal/index';
+export { transpile, transpileSync } from './transpile';
+/**
+ * The compiler is the utility that brings together many tools to build optimized components,
+ * such as a transpiler, bundler, and minifier, along with many internal optimizations to
+ * create small efficient compoennts. When using the CLI, the `rindo build` command uses
+ * the compiler for the various builds, such as a production build, or watch mode during
+ * development. If only one file should be transformed then the `transpile()` function
+ * should be used instead.
+ *
+ * Given a Rindo config, this method asynchronously returns a `Compiler` instance. The
+ * config provided should already be created using the `loadConfig({...})` method.
+ */
+export declare const createCompiler: (config: Config) => Promise<Compiler>;
+export declare const createPrerenderer: (config: Config) => Promise<{
+    start: (opts: PrerenderStartOptions) => Promise<PrerenderResults>;
+}>;
+/**
+ * The compiler uses a `CompilerSystem` instance to access any file system reads and writes.
+ * When used from the CLI, the CLI will provide its own system based on NodeJS. This method
+ * provide a compiler system is in-memory only and independent of any platform.
+ */
+export declare const createSystem: () => CompilerSystem;
+/**
+ * The `dependencies` array is only informational and provided to state which versions of
+ * dependencies the compiler was built and works with. For example, the version of TypeScript,
+ * Rollup and Terser used for this version of Rindo are listed here.
+ */
+export declare const dependencies: CompilerDependency[];
+export interface CompilerDependency {
+    name: string;
+    version: string;
+    main: string;
+    resources?: string[];
+}
+/**
+ * The `loadConfig(init)` method is used to take raw config information and transform it into a
+ * usable config object for the compiler and dev-server. The `init` argument should be given
+ * an already created system and logger which can also be used by the compiler.
+ */
+export declare const loadConfig: (init?: LoadConfigInit) => Promise<LoadConfigResults>;
+/**
+ * Utility function used by the compiler to optimize CSS.
+ */
+export declare const optimizeCss: (cssInput?: OptimizeCssInput) => Promise<OptimizeCssOutput>;
+/**
+ * Utility function used by the compiler to optimize JavaScript. Knowing the JavaScript target
+ * will further apply minification optimizations beyond usual minification.
+ */
+export declare const optimizeJs: (jsInput?: OptimizeJsInput) => Promise<OptimizeJsOutput>;
+/**
+ * Utility of the `path` API providied by NodeJS, but capable of running in any environment.
+ */
+export declare const path: PlatformPath;
+/**
+ * Current version of `@rindo/core`.
+ */
+export declare const version: string;
+export declare const versions: {
+    rindo: string;
+    typescript: string;
+    rollup: string;
+    terser: string;
+};
+/**
+ * Current version's emoji :)
+ */
+export declare const vermoji: string;
+/**
+ * Compiler's unique build ID.
+ */
+export declare const buildId: string;
+export { Compiler, CompilerBuildResults, CompilerSystem, CompilerWatcher, CompileScriptMinifyOptions, Config, Diagnostic, LoadConfigInit, LoadConfigResults, OptimizeCssInput, OptimizeCssOutput, OptimizeJsInput, OptimizeJsOutput, TranspileOptions, TranspileResults, };