Chore: Upgrade to AIK & Massive Overhaul to internal processing #78
|
|
@ -177,10 +177,10 @@ export default defineIntegration({
|
|||
|
|
||||
|
||||
// Setup GhostCMS Theme Provider
|
||||
localIntegration(
|
||||
!options.ThemeProvider?.disableThemeProvider,
|
||||
```suggestion
} else if (verbose) {
GhostIntegrationLogger.info(c.gray("Theme Provider is disabled"));
}
```
same here same here
same here same here
same here same here
is there a reason for not importing it at the top of the file? if yes, I think you can use is there a reason for not importing it at the top of the file? if yes, I think you can use `resolve` from `createResolver` for the path
This is simply to display any new version during dev-mode only... There is a check for latest version and it compares the local version :D This is simply to display any new version during dev-mode only... There is a check for latest version and it compares the local version :D
ah this pulls the version from the user's project? ah this pulls the version from the user's project?
I ALWAYS FORGET YOU CAN DO I ALWAYS FORGET YOU CAN DO `else if` vscode should complain if you do an `else { if()` lol
i think if you have eslint you can enable such a rule i think if you have eslint you can enable such a rule
grabs the current installed one from grabs the current installed one from `astro-ghostcms` local version and compares to the latestversion from NPM :P I did actually try to use the `resolve()` util but that just grabbed the playgrounds package.json ironically...
Instead of all these manual checks for Or could be a Florian special and return a console log function: Instead of all these manual checks for `verbose` you'd probably be better off with a util function which checks it instead.
```ts
const log = message => {
if (verbose) {
console.log(...)
}
}
```
Or could be a Florian special and return a console log function:
```ts
const createLogger = verbose => message => {
if (verbose) {
console.log(...)
}
}
const log = createLogger(options.verbose)
log(whatever) // now you don't have to check everywhere
```
added in new commit, since im not using console.log had to modify it for my usage a little added in new commit, since im not using console.log had to modify it for my usage a little
Okay i fixed that issue. Now using Okay i fixed that issue. Now using `resolve()` properly 😄
This logging function could also be extracted This logging function could also be extracted
```ts
const formattedMessage = message => `${c.bold(c.blue("👻 Astro-GhostCMS"))}${c.gray("/")}${c.blue(message)}`
```
Updated... Updated...
```ts
// Configure Loggers
const GhostLogger = logger.fork(c.bold(c.blue("👻 Astro-GhostCMS")));
const loggerTagged = (message: string) => {
return logger.fork(`${c.bold(c.blue("👻 Astro-GhostCMS"))}${c.gray("/")}${c.blue(message)}`)
}
// Configure ENV Logger
const GhostENVLogger = loggerTagged("ENV Check");
// Configure Integration Loggers & verbose logging
const GhostIntegrationLogger = loggerTagged("Integrations");
// Configure Route Logger & verbose logging
const GhostRouteLogger = loggerTagged("Router");
```
|
||||
!options.ThemeProvider.disableThemeProvider,
|
||||
```suggestion
} else if (verbose) {
GhostIntegrationLogger.info(c.gray("Theme Provider is disabled"));
}
```
same here same here
same here same here
same here same here
is there a reason for not importing it at the top of the file? if yes, I think you can use is there a reason for not importing it at the top of the file? if yes, I think you can use `resolve` from `createResolver` for the path
This is simply to display any new version during dev-mode only... There is a check for latest version and it compares the local version :D This is simply to display any new version during dev-mode only... There is a check for latest version and it compares the local version :D
ah this pulls the version from the user's project? ah this pulls the version from the user's project?
I ALWAYS FORGET YOU CAN DO I ALWAYS FORGET YOU CAN DO `else if` vscode should complain if you do an `else { if()` lol
i think if you have eslint you can enable such a rule i think if you have eslint you can enable such a rule
grabs the current installed one from grabs the current installed one from `astro-ghostcms` local version and compares to the latestversion from NPM :P I did actually try to use the `resolve()` util but that just grabbed the playgrounds package.json ironically...
Instead of all these manual checks for Or could be a Florian special and return a console log function: Instead of all these manual checks for `verbose` you'd probably be better off with a util function which checks it instead.
```ts
const log = message => {
if (verbose) {
console.log(...)
}
}
```
Or could be a Florian special and return a console log function:
```ts
const createLogger = verbose => message => {
if (verbose) {
console.log(...)
}
}
const log = createLogger(options.verbose)
log(whatever) // now you don't have to check everywhere
```
added in new commit, since im not using console.log had to modify it for my usage a little added in new commit, since im not using console.log had to modify it for my usage a little
Okay i fixed that issue. Now using Okay i fixed that issue. Now using `resolve()` properly 😄
This logging function could also be extracted This logging function could also be extracted
```ts
const formattedMessage = message => `${c.bold(c.blue("👻 Astro-GhostCMS"))}${c.gray("/")}${c.blue(message)}`
```
Updated... Updated...
```ts
// Configure Loggers
const GhostLogger = logger.fork(c.bold(c.blue("👻 Astro-GhostCMS")));
const loggerTagged = (message: string) => {
return logger.fork(`${c.bold(c.blue("👻 Astro-GhostCMS"))}${c.gray("/")}${c.blue(message)}`)
}
// Configure ENV Logger
const GhostENVLogger = loggerTagged("ENV Check");
// Configure Integration Loggers & verbose logging
const GhostIntegrationLogger = loggerTagged("Integrations");
// Configure Route Logger & verbose logging
const GhostRouteLogger = loggerTagged("Router");
```
|
||||
"Theme Provider",
|
||||
ghostThemeProvider({
|
||||
theme: options.ThemeProvider?.theme,
|
||||
```suggestion
} else if (verbose) {
GhostIntegrationLogger.info(c.gray("Theme Provider is disabled"));
}
```
same here same here
same here same here
same here same here
is there a reason for not importing it at the top of the file? if yes, I think you can use is there a reason for not importing it at the top of the file? if yes, I think you can use `resolve` from `createResolver` for the path
This is simply to display any new version during dev-mode only... There is a check for latest version and it compares the local version :D This is simply to display any new version during dev-mode only... There is a check for latest version and it compares the local version :D
ah this pulls the version from the user's project? ah this pulls the version from the user's project?
I ALWAYS FORGET YOU CAN DO I ALWAYS FORGET YOU CAN DO `else if` vscode should complain if you do an `else { if()` lol
i think if you have eslint you can enable such a rule i think if you have eslint you can enable such a rule
grabs the current installed one from grabs the current installed one from `astro-ghostcms` local version and compares to the latestversion from NPM :P I did actually try to use the `resolve()` util but that just grabbed the playgrounds package.json ironically...
Instead of all these manual checks for Or could be a Florian special and return a console log function: Instead of all these manual checks for `verbose` you'd probably be better off with a util function which checks it instead.
```ts
const log = message => {
if (verbose) {
console.log(...)
}
}
```
Or could be a Florian special and return a console log function:
```ts
const createLogger = verbose => message => {
if (verbose) {
console.log(...)
}
}
const log = createLogger(options.verbose)
log(whatever) // now you don't have to check everywhere
```
added in new commit, since im not using console.log had to modify it for my usage a little added in new commit, since im not using console.log had to modify it for my usage a little
Okay i fixed that issue. Now using Okay i fixed that issue. Now using `resolve()` properly 😄
This logging function could also be extracted This logging function could also be extracted
```ts
const formattedMessage = message => `${c.bold(c.blue("👻 Astro-GhostCMS"))}${c.gray("/")}${c.blue(message)}`
```
Updated... Updated...
```ts
// Configure Loggers
const GhostLogger = logger.fork(c.bold(c.blue("👻 Astro-GhostCMS")));
const loggerTagged = (message: string) => {
return logger.fork(`${c.bold(c.blue("👻 Astro-GhostCMS"))}${c.gray("/")}${c.blue(message)}`)
}
// Configure ENV Logger
const GhostENVLogger = loggerTagged("ENV Check");
// Configure Integration Loggers & verbose logging
const GhostIntegrationLogger = loggerTagged("Integrations");
// Configure Route Logger & verbose logging
const GhostRouteLogger = loggerTagged("Router");
```
|
||||
theme: options.ThemeProvider.theme,
|
||||
```suggestion
} else if (verbose) {
GhostIntegrationLogger.info(c.gray("Theme Provider is disabled"));
}
```
same here same here
same here same here
same here same here
is there a reason for not importing it at the top of the file? if yes, I think you can use is there a reason for not importing it at the top of the file? if yes, I think you can use `resolve` from `createResolver` for the path
This is simply to display any new version during dev-mode only... There is a check for latest version and it compares the local version :D This is simply to display any new version during dev-mode only... There is a check for latest version and it compares the local version :D
ah this pulls the version from the user's project? ah this pulls the version from the user's project?
I ALWAYS FORGET YOU CAN DO I ALWAYS FORGET YOU CAN DO `else if` vscode should complain if you do an `else { if()` lol
i think if you have eslint you can enable such a rule i think if you have eslint you can enable such a rule
grabs the current installed one from grabs the current installed one from `astro-ghostcms` local version and compares to the latestversion from NPM :P I did actually try to use the `resolve()` util but that just grabbed the playgrounds package.json ironically...
Instead of all these manual checks for Or could be a Florian special and return a console log function: Instead of all these manual checks for `verbose` you'd probably be better off with a util function which checks it instead.
```ts
const log = message => {
if (verbose) {
console.log(...)
}
}
```
Or could be a Florian special and return a console log function:
```ts
const createLogger = verbose => message => {
if (verbose) {
console.log(...)
}
}
const log = createLogger(options.verbose)
log(whatever) // now you don't have to check everywhere
```
added in new commit, since im not using console.log had to modify it for my usage a little added in new commit, since im not using console.log had to modify it for my usage a little
Okay i fixed that issue. Now using Okay i fixed that issue. Now using `resolve()` properly 😄
This logging function could also be extracted This logging function could also be extracted
```ts
const formattedMessage = message => `${c.bold(c.blue("👻 Astro-GhostCMS"))}${c.gray("/")}${c.blue(message)}`
```
Updated... Updated...
```ts
// Configure Loggers
const GhostLogger = logger.fork(c.bold(c.blue("👻 Astro-GhostCMS")));
const loggerTagged = (message: string) => {
return logger.fork(`${c.bold(c.blue("👻 Astro-GhostCMS"))}${c.gray("/")}${c.blue(message)}`)
}
// Configure ENV Logger
const GhostENVLogger = loggerTagged("ENV Check");
// Configure Integration Loggers & verbose logging
const GhostIntegrationLogger = loggerTagged("Integrations");
// Configure Route Logger & verbose logging
const GhostRouteLogger = loggerTagged("Router");
```
|
||||
verbose,
|
||||
})
|
||||
);
|
||||
|
|
|
|||
```suggestion
} else if (verbose) {
GhostIntegrationLogger.info(c.gray("Theme Provider is disabled"));
}
```
```suggestion
} else if (verbose) {
GhostIntegrationLogger.info(c.gray("Theme Provider is disabled"));
}
```
same here same here
same here same here
same here same here
same here same here
same here same here
same here same here
is there a reason for not importing it at the top of the file? if yes, I think you can use is there a reason for not importing it at the top of the file? if yes, I think you can use `resolve` from `createResolver` for the path
is there a reason for not importing it at the top of the file? if yes, I think you can use is there a reason for not importing it at the top of the file? if yes, I think you can use `resolve` from `createResolver` for the path
This is simply to display any new version during dev-mode only... There is a check for latest version and it compares the local version :D This is simply to display any new version during dev-mode only... There is a check for latest version and it compares the local version :D
This is simply to display any new version during dev-mode only... There is a check for latest version and it compares the local version :D This is simply to display any new version during dev-mode only... There is a check for latest version and it compares the local version :D
ah this pulls the version from the user's project? ah this pulls the version from the user's project?
ah this pulls the version from the user's project? ah this pulls the version from the user's project?
I ALWAYS FORGET YOU CAN DO I ALWAYS FORGET YOU CAN DO `else if` vscode should complain if you do an `else { if()` lol
I ALWAYS FORGET YOU CAN DO I ALWAYS FORGET YOU CAN DO `else if` vscode should complain if you do an `else { if()` lol
i think if you have eslint you can enable such a rule i think if you have eslint you can enable such a rule
i think if you have eslint you can enable such a rule i think if you have eslint you can enable such a rule
grabs the current installed one from grabs the current installed one from `astro-ghostcms` local version and compares to the latestversion from NPM :P I did actually try to use the `resolve()` util but that just grabbed the playgrounds package.json ironically...
grabs the current installed one from grabs the current installed one from `astro-ghostcms` local version and compares to the latestversion from NPM :P I did actually try to use the `resolve()` util but that just grabbed the playgrounds package.json ironically...
Instead of all these manual checks for Or could be a Florian special and return a console log function: Instead of all these manual checks for `verbose` you'd probably be better off with a util function which checks it instead.
```ts
const log = message => {
if (verbose) {
console.log(...)
}
}
```
Or could be a Florian special and return a console log function:
```ts
const createLogger = verbose => message => {
if (verbose) {
console.log(...)
}
}
const log = createLogger(options.verbose)
log(whatever) // now you don't have to check everywhere
```
Instead of all these manual checks for Or could be a Florian special and return a console log function: Instead of all these manual checks for `verbose` you'd probably be better off with a util function which checks it instead.
```ts
const log = message => {
if (verbose) {
console.log(...)
}
}
```
Or could be a Florian special and return a console log function:
```ts
const createLogger = verbose => message => {
if (verbose) {
console.log(...)
}
}
const log = createLogger(options.verbose)
log(whatever) // now you don't have to check everywhere
```
added in new commit, since im not using console.log had to modify it for my usage a little added in new commit, since im not using console.log had to modify it for my usage a little
added in new commit, since im not using console.log had to modify it for my usage a little added in new commit, since im not using console.log had to modify it for my usage a little
Okay i fixed that issue. Now using Okay i fixed that issue. Now using `resolve()` properly 😄
Okay i fixed that issue. Now using Okay i fixed that issue. Now using `resolve()` properly 😄
This logging function could also be extracted This logging function could also be extracted
```ts
const formattedMessage = message => `${c.bold(c.blue("👻 Astro-GhostCMS"))}${c.gray("/")}${c.blue(message)}`
```
This logging function could also be extracted This logging function could also be extracted
```ts
const formattedMessage = message => `${c.bold(c.blue("👻 Astro-GhostCMS"))}${c.gray("/")}${c.blue(message)}`
```
Updated... Updated...
```ts
// Configure Loggers
const GhostLogger = logger.fork(c.bold(c.blue("👻 Astro-GhostCMS")));
const loggerTagged = (message: string) => {
return logger.fork(`${c.bold(c.blue("👻 Astro-GhostCMS"))}${c.gray("/")}${c.blue(message)}`)
}
// Configure ENV Logger
const GhostENVLogger = loggerTagged("ENV Check");
// Configure Integration Loggers & verbose logging
const GhostIntegrationLogger = loggerTagged("Integrations");
// Configure Route Logger & verbose logging
const GhostRouteLogger = loggerTagged("Router");
```
Updated... Updated...
```ts
// Configure Loggers
const GhostLogger = logger.fork(c.bold(c.blue("👻 Astro-GhostCMS")));
const loggerTagged = (message: string) => {
return logger.fork(`${c.bold(c.blue("👻 Astro-GhostCMS"))}${c.gray("/")}${c.blue(message)}`)
}
// Configure ENV Logger
const GhostENVLogger = loggerTagged("ENV Check");
// Configure Integration Loggers & verbose logging
const GhostIntegrationLogger = loggerTagged("Integrations");
// Configure Route Logger & verbose logging
const GhostRouteLogger = loggerTagged("Router");
```
|
||||
|
|
@ -6,7 +6,7 @@ import c from "picocolors";
|
|||
|
You can probably resolve these paths instead of exporting it from your package? You can probably resolve these paths instead of exporting it from your package?
You can probably resolve these paths instead of exporting it from your package? You can probably resolve these paths instead of exporting it from your package?
I was told that any Injected route had to be from an export.... I'd be interested in that alternative... I was told that any Injected route had to be from an export.... I'd be interested in that alternative...
I was told that any Injected route had to be from an export.... I'd be interested in that alternative... I was told that any Injected route had to be from an export.... I'd be interested in that alternative...
They did in the old days before They did in the old days before `createResolver` ❤️ it just can't be a virtual module
They did in the old days before They did in the old days before `createResolver` ❤️ it just can't be a virtual module
Yeah.... Thats updated now across the board... and those exports for Yeah.... Thats updated now across the board... and those exports for `/rss-routes` and `/open-graph` are now moved to `resolve()`
Yeah.... Thats updated now across the board... and those exports for Yeah.... Thats updated now across the board... and those exports for `/rss-routes` and `/open-graph` are now moved to `resolve()`
|
||||
export default defineIntegration({
|
||||
name: "@matthiesenxyz/astro-ghostcms-rss",
|
||||
optionsSchema: z.object({
|
||||
verbose: z.boolean().optional().default(false),
|
||||
|
You can probably resolve these paths instead of exporting it from your package? You can probably resolve these paths instead of exporting it from your package?
I was told that any Injected route had to be from an export.... I'd be interested in that alternative... I was told that any Injected route had to be from an export.... I'd be interested in that alternative...
They did in the old days before They did in the old days before `createResolver` ❤️ it just can't be a virtual module
Yeah.... Thats updated now across the board... and those exports for Yeah.... Thats updated now across the board... and those exports for `/rss-routes` and `/open-graph` are now moved to `resolve()`
|
||||
verbose: z.coerce.boolean().optional(),
|
||||
|
You can probably resolve these paths instead of exporting it from your package? You can probably resolve these paths instead of exporting it from your package?
I was told that any Injected route had to be from an export.... I'd be interested in that alternative... I was told that any Injected route had to be from an export.... I'd be interested in that alternative...
They did in the old days before They did in the old days before `createResolver` ❤️ it just can't be a virtual module
Yeah.... Thats updated now across the board... and those exports for Yeah.... Thats updated now across the board... and those exports for `/rss-routes` and `/open-graph` are now moved to `resolve()`
|
||||
}),
|
||||
plugins: [...corePlugins],
|
||||
setup({ options }) {
|
||||
|
|
|
|||
|
You can probably resolve these paths instead of exporting it from your package? You can probably resolve these paths instead of exporting it from your package?
You can probably resolve these paths instead of exporting it from your package? You can probably resolve these paths instead of exporting it from your package?
I was told that any Injected route had to be from an export.... I'd be interested in that alternative... I was told that any Injected route had to be from an export.... I'd be interested in that alternative...
I was told that any Injected route had to be from an export.... I'd be interested in that alternative... I was told that any Injected route had to be from an export.... I'd be interested in that alternative...
They did in the old days before They did in the old days before `createResolver` ❤️ it just can't be a virtual module
They did in the old days before They did in the old days before `createResolver` ❤️ it just can't be a virtual module
Yeah.... Thats updated now across the board... and those exports for Yeah.... Thats updated now across the board... and those exports for `/rss-routes` and `/open-graph` are now moved to `resolve()`
Yeah.... Thats updated now across the board... and those exports for Yeah.... Thats updated now across the board... and those exports for `/rss-routes` and `/open-graph` are now moved to `resolve()`
|
||||
|
|
@ -6,7 +6,7 @@ import c from "picocolors";
|
|||
export default defineIntegration({
|
||||
name: "@matthiesenxyz/astro-ghostcms-satoriog",
|
||||
optionsSchema: z.object({
|
||||
verbose: z.boolean().optional().default(false),
|
||||
verbose: z.coerce.boolean().optional(),
|
||||
}),
|
||||
plugins: [...corePlugins],
|
||||
setup({ options }) {
|
||||
|
|
|
|||
|
|
@ -6,16 +6,15 @@ import c from "picocolors";
|
|||
export default defineIntegration({
|
||||
name: "@matthiesenxyz/astro-ghostcms-themeprovider",
|
||||
optionsSchema: z.object({
|
||||
theme: z
|
||||
.string()
|
||||
.optional()
|
||||
.default("@matthiesenxyz/astro-ghostcms-theme-default"),
|
||||
verbose: z.boolean().optional().default(false),
|
||||
theme: z.string(),
|
||||
verbose: z.coerce.boolean().optional(),
|
||||
}),
|
||||
plugins: [...corePlugins],
|
||||
setup({ options }) {
|
||||
const { resolve } = createResolver(import.meta.url);
|
||||
|
||||
const DEFAULT_THEME = "@matthiesenxyz/astro-ghostcms-theme-default";
|
||||
|
||||
return {
|
||||
"astro:config:setup": ({ watchIntegration, injectRoute, logger }) => {
|
||||
watchIntegration(resolve());
|
||||
|
|
@ -37,7 +36,7 @@ export default defineIntegration({
|
|||
);
|
||||
|
||||
|
||||
if (options.theme === "@matthiesenxyz/astro-ghostcms-theme-default") {
|
||||
if (options.theme === DEFAULT_THEME) {
|
||||
verboseLogsInfo(
|
||||
c.blue("No theme is set, injecting default theme"),
|
||||
);
|
||||
|
|
|
|||
|
|
@ -13,6 +13,7 @@ describe("GhostUserConfigSchema", () => {
|
|||
enableRSSFeed: true,
|
||||
enableOGImages: true,
|
||||
verbose: false,
|
||||
Integrations: {},
|
||||
};
|
||||
|
||||
const result = GhostUserConfigSchema.safeParse(validConfig);
|
||||
|
|
|
|||
|
|
@ -13,34 +13,38 @@ export const GhostUserConfigSchema = z.object({
|
|||
* })
|
||||
* ],
|
||||
* }); */
|
||||
ghostURL: z.string().url().optional(),
|
||||
ghostURL: z.coerce.string().url("Must be a URL").optional(),
|
||||
/** OPTIONAL - Configure the Theme Provider
|
||||
* @ This option allows the user to configure the Theme Provider
|
||||
*/
|
||||
ThemeProvider: z
|
||||
.object({
|
||||
/** OPTIONAL - Disable the theme provider
|
||||
* @default false
|
||||
*/
|
||||
disableThemeProvider: z.boolean().optional().default(false),
|
||||
disableThemeProvider: z.coerce.boolean(),
|
||||
/** OPTIONAL - Set the theme you want to use
|
||||
* @default "@matthiesenxyz/astro-ghostcms-theme-default"
|
||||
*/
|
||||
theme: z
|
||||
.string()
|
||||
.optional()
|
||||
.default("@matthiesenxyz/astro-ghostcms-theme-default"),
|
||||
theme: z.string(),
|
||||
})
|
||||
.optional(),
|
||||
.optional()
|
||||
.default({
|
||||
disableThemeProvider: false,
|
||||
theme: "@matthiesenxyz/astro-ghostcms-theme-default"
|
||||
}),
|
||||
/** Allows the user to disable the provided 404 page */
|
||||
disableDefault404: z.boolean().optional().default(false),
|
||||
disableDefault404: z.coerce.boolean().optional(),
|
||||
/** Allows the user to disable the provided RSS Feed */
|
||||
enableRSSFeed: z.boolean().optional().default(true),
|
||||
enableRSSFeed: z.coerce.boolean().optional().default(true),
|
||||
/** Allows the user to Enable or Disable the default Satori OG Image Generation
|
||||
* @default true
|
||||
*/
|
||||
enableOGImages: z.boolean().optional().default(true),
|
||||
enableOGImages: z.coerce.boolean().optional().default(true),
|
||||
/** Allows the user to turn on/off Full Console Logs
|
||||
* @default true
|
||||
*/
|
||||
verbose: z.boolean().optional().default(false),
|
||||
verbose: z.coerce.boolean().optional(),
|
||||
/** OPTIONAL - Integrations Configuration
|
||||
* This option allows the user to configure the included integrations
|
||||
* Options shown are the availble options
|
||||
|
|
@ -60,7 +64,7 @@ export const GhostUserConfigSchema = z.object({
|
|||
*/
|
||||
sitemap: z.custom<SitemapOptions>().optional(),
|
||||
})
|
||||
.optional(),
|
||||
.optional().default({}),
|
||||
});
|
||||
|
||||
/** USER CONFIGURATION SCHEMA */
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ export default defineConfig({
|
|||
ThemeProvider: {
|
||||
theme: "@matthiesenxyz/astro-ghostcms-brutalbyelian",
|
||||
},
|
||||
verbose: false,
|
||||
verbose: true,
|
||||
}),
|
||||
],
|
||||
});
|
||||
|
|
|
|||
same here
same here
same here
same here
same here
same here
is there a reason for not importing it at the top of the file? if yes, I think you can use
resolvefromcreateResolverfor the pathis there a reason for not importing it at the top of the file? if yes, I think you can use
resolvefromcreateResolverfor the pathThis is simply to display any new version during dev-mode only... There is a check for latest version and it compares the local version :D
This is simply to display any new version during dev-mode only... There is a check for latest version and it compares the local version :D
ah this pulls the version from the user's project?
ah this pulls the version from the user's project?
I ALWAYS FORGET YOU CAN DO
else ifvscode should complain if you do anelse { if()lolI ALWAYS FORGET YOU CAN DO
else ifvscode should complain if you do anelse { if()loli think if you have eslint you can enable such a rule
i think if you have eslint you can enable such a rule
grabs the current installed one from
astro-ghostcmslocal version and compares to the latestversion from NPM :P I did actually try to use theresolve()util but that just grabbed the playgrounds package.json ironically...grabs the current installed one from
astro-ghostcmslocal version and compares to the latestversion from NPM :P I did actually try to use theresolve()util but that just grabbed the playgrounds package.json ironically...Instead of all these manual checks for
verboseyou'd probably be better off with a util function which checks it instead.Or could be a Florian special and return a console log function:
Instead of all these manual checks for
verboseyou'd probably be better off with a util function which checks it instead.Or could be a Florian special and return a console log function:
added in new commit, since im not using console.log had to modify it for my usage a little
added in new commit, since im not using console.log had to modify it for my usage a little
Okay i fixed that issue. Now using
resolve()properly 😄Okay i fixed that issue. Now using
resolve()properly 😄This logging function could also be extracted
This logging function could also be extracted
Updated...
Updated...