decaporg/one-click-hugo-cms

Hugo template with Decap CMS

one-click-hugo-cms's Issues

Does not run with `netlify dev` command

- Do you want to request a feature or report a bug?
Bug.

- What is the current behavior?
After running npm install, the command npm start works, but netlify dev does not, once it's set up.

- If the current behavior is a bug, please provide the steps to reproduce.

1. Create a new project (mine is based at commit 9d20f73dfbaea4531ab4b3e36fb9c9a56687743a).
2. Run npm install to install dependencies.
3. Authenticate and link the netlify CLI to the project.
4. Run netlify dev and see the following error:

   ◈ Netlify Dev ◈
   ◈ Starting Netlify Dev with hugo
   Error: "hugo" could not be found in your PATH. Please make sure that "hugo" is installed and available in your PATH
   

5. Run PATH=$PATH:node_modules/hugo-bin/vendor netlify dev and see the message

   WARN 2020/05/02 21:58:59 found no layout file for "HTML" for kind "hom
   

- What is the expected behavior?
netlify dev should serve the generated site.
- Please mention your node.js, NPM, Hugo and operating system version.

node v13.2.0 (and 14.1.0)
npm 6.14.4
hugo -- none installed on the system
MacOS 10.15.4 (19E287)

Found no layout file for “HTML” for kind “taxonomy”: You should create a template file which matches Hugo Layouts Lookup Rules for this combination

- Do you want to request a feature or report a bug?

- What is the current behavior?

- If the current behavior is a bug, please provide the steps to reproduce.

- What is the expected behavior?

- Please mention your node.js, NPM, Hugo and operating system version.

Serve site from subdirectory

Hello I am trying to serve this site from a subdirectory on netlify. siteurl.com/blog

I am having trouble achieving this on netlify so I decided to try to get it working locally first but I am having trouble with that as well.
I have set the baseUrl in site/config.toml like so
baseurl = "/blog"
But when I run npm run preview it opens the site at localhost:3000 instead of localhost:3000/blog while the latter url produces a 404 error.

Any assistance with this would be greatly appreciated and I am happy to provide any clarifying information

Git Gateway Error accessing Admin panel on a brand-new one-click deployment

- Do you want to request a feature or report a bug?
Bug.

- What is the current behavior?

I get the following error when I try to log in with an existing Netlify Identity user account on a brand-new NetlifyCMS Hugo starter template site.

Git Gateway Error: Please ask your site administrator to reissue the Git Gateway token.

I cannot proceed to the next screen. The underlying response is a HTTP 401 with the following payload

{
  "message": "Bad credentials",
  "documentation_url": "https://docs.github.com/rest"
}

- If the current behavior is a bug, please provide the steps to reproduce.

1. Launch a new NetlifyCMS Hugo starter template, leaving all defaults in, i.e. Git Gateway and Netlify Identity are enabled, GitHub API token is set...
2. Accept the email invite that will arrive when the website is finished deploying
3. Sign up on the newly deployed site and navigate to admin page on /admin
4. Error described above appears and you're not allowed to proceed further.

- What is the expected behavior?

If I attempt to log onto the NetlifyCMS Admin dashboard with an existing Netlify Identity account, I should be allowed to proceed.

- Please mention your node.js, NPM, Hugo and operating system version.

It's the Netlify-hosted version pointing at the HEAD of this repo, so whatever those versions are. This happens both on Chrome and Firefox running on my Linux machine.

Local development fails: `npm install` and `npm install --force` fail with latest Node and NPM

- Do you want to request a feature or report a bug?

Bug

- What is the current behavior?

Using latest Node and NPM, both npm install and npm install --force fail to complete successfully.

This means version v16.3.0 and 7.15.1 respectivly.

- If the current behavior is a bug, please provide the steps to reproduce.

root@ubuntu-s-1vcpu-1gb-nyc1-01:~/# git clone https://github.com/netlify-templates/one-click-hugo-cms foo
root@ubuntu-s-1vcpu-1gb-nyc1-01:~/# cd foo
root@ubuntu-s-1vcpu-1gb-nyc1-01:~/foo# node --version
v16.3.0
root@ubuntu-s-1vcpu-1gb-nyc1-01:~/foo# npm --version
7.15.1
root@ubuntu-s-1vcpu-1gb-nyc1-01:~/foo# npm install
npm notice
npm notice New minor version of npm available! 7.15.1 -> 7.17.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v7.17.0
npm notice Run npm install -g [email protected] to update!
npm notice
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   dev react@"^16.8.6" from the root project
npm ERR!   peer react@"^16.8.4 || ^17.0.0" from [email protected]
npm ERR!   node_modules/netlify-cms-app
npm ERR!     dev netlify-cms-app@"^2.15.19" from the root project
npm ERR!   51 more (react-dom, @emotion/core, @emotion/styled, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^17.0.1" from [email protected]
npm ERR! node_modules/netlify-cms-widget-colorstring/node_modules/validate-color
npm ERR!   validate-color@"^2.1.0" from [email protected]
npm ERR!   node_modules/netlify-cms-widget-colorstring
npm ERR!     netlify-cms-widget-colorstring@"^1.1.1" from [email protected]
npm ERR!     node_modules/netlify-cms-app
npm ERR!       dev netlify-cms-app@"^2.15.19" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /root/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-06-12T23_26_41_357Z-debug.log
root@ubuntu-s-1vcpu-1gb-nyc1-01:~/foo#

- What is the expected behavior?

I would expect npm install to complete with warnings are not.
I would expect npm install --force to complete (output not included in issue)

- Please mention your node.js, NPM, Hugo and operating system version.

I tried this on both Ubuntu 20.04 and the latest macOS, with the same versions of npm, node:
root@ubuntu-s-1vcpu-1gb-nyc1-01:/foo# node --version
v16.3.0
root@ubuntu-s-1vcpu-1gb-nyc1-01:/foo# npm --version
7.15.1

Typo in CSS-property in _border-radius.css

You are using

.br--bottom-l {
		border-radius-top-left: 0;
		border-radius-top-right: 0;
}

correct, however, would be

.br--bottom-l {
		border-top-left-radius: 0;
		border-top-right-radius: 0;
}

I am going to fix this in a MR.

CMS update issue

Seems that since the NetlifyCMS update, deploying a new instance of one-click-hugo-cms results in the right-hand pane of the CMS not having its usual WYSIWIG features.

Below: Normal right-hand pane view + current right-hand pane view with newly launched one-click-hugo-cms sites.

(Note: This also happens w/the NetlifyCMS-Gatsby site, with a slight difference: after initial deploy, once you update to NetCMS2.8.0, the right-pane loses its WYSIWIG display features.)

switch from master to main

switch default branch from master to main to get rid of master and also help with integrations

Absolute URLs in the list of posts

If you have defined a baseurl in config.toml then https://github.com/netlify-templates/one-click-hugo-cms/blob/master/site/layouts/_default/li.html will write absolute URLs in the hrefs.

Not wrong but makes testing across different environments trickier.

Is there a reason why .Permalink is being used instead of .RelPermalink to write the links?

Uncaught SyntaxError: Unexpected token <

I did a fresh clone of this repo yesterday and found a bug.

- Do you want to request a feature or report a bug?
bug

- What is the current behavior?
Locally (using yarn start): Console output Uncaught SyntaxError: Unexpected token <.
Netlify live version: 404 for app.js.

- If the current behavior is a bug, please provide the steps to reproduce.
Clone, run yarn and then yarn start. Open up dev tools an look a the error in the console.

- What is the expected behavior?
No error. No 404 Not Found for app.js.

- Please mention your node.js, NPM, Hugo and operating system version.
node v10.16.0
npm 6.4.1
Hugo v0.56.3-F637A1EA windows/amd64 BuildDate: 2019-07-31T12:51:49Z
Windows 10

Pages appear in reverse order on /post/

.ByDate shouldn't be necessary since it causes pages to appear as oldest to newest.
here: #60

Bug: 1-click site generation fails

- Do you want to request a feature or report a bug?

Bug

- What is the current behavior?

The 1-click site generation does not work

- If the current behavior is a bug, please provide the steps to reproduce.

• Click the "Deploy to Netlify button"
• Connect with GitHub
• Provide name for repo
• Hit continue button

- What is the expected behavior?

• The new repo is populated as advertised with everything set up

- Please mention your node.js, NPM, Hugo and operating system version.

/admin load fails

Error loading the CMS configuration
Config Errors:

YAMLException: end of the stream or a document separator is expected at line 153, column 19:
    <div style="height: 0; width: 0; position: absolut ... 
                      ^

Check your config.yml file..

Node 12.13 lts Ubuntu 18

Switching to private repo in Github makes entries dissapear?

When I turn my github repo, with one-click-hugo-cms, to private. All my entries dissapear in the admin area. When I make the repo public they appear. Do I have make some Identity setting somewhere?

New stewardship and direction

Howdy peeps,

Prince from Netlify! We're going to be working on this project to bringing the latest changes of Hugo so you all have the best experience. For now, my main goal is to break it down into a few phases:

• Updating dependencies so deploying is smooth
• Migrating into new pipelines so we follow best practices
• Optimizing the layouts for accessibility

Is there anything that y'all have for suggestions for the project? Is there prior art you'd like involved? We're happy to listen to folks out here using Hugo.

Newly created Git repository with does not deploy to Netlify (error: spawn EACCES)

I have deployed a clone of this repository to Netlify and it worked fine.
Then I decided I wanted to start a fresh Git repository, so I created a new one, placed all the code from the cloned repo into the newly created repo and tried to deploy; it fails.

During the build, Netlify returns an error while trying to execute Hugo:

10:03:37 PM: Starting 'hugo'...
10:03:37 PM: [21:03:37]
10:03:37 PM: 'hugo' errored after 14 ms
10:03:37 PM: [21:03:37]
10:03:37 PM: Error: spawn EACCES
10:03:37 PM:     at ChildProcess.spawn (internal/child_process.js:313:11)
10:03:37 PM:     at Object.exports.spawn (child_process.js:508:9)
10:03:37 PM:     at buildSite (/opt/build/repo/gulpfile.babel.js:81:13)
10:03:37 PM:     at Gulp.<anonymous> (/opt/build/repo/gulpfile.babel.js:23:27)
10:03:37 PM:     at module.exports (/opt/build/repo/node_modules/orchestrator/lib/runTask.js:34:7)
10:03:37 PM:     at Gulp.Orchestrator._runTask (/opt/build/repo/node_modules/orchestrator/index.js:273:3)
10:03:37 PM:     at Gulp.Orchestrator._runStep (/opt/build/repo/node_modules/orchestrator/index.js:214:10)
10:03:37 PM:     at Gulp.Orchestrator.start (/opt/build/repo/node_modules/orchestrator/index.js:134:8)
10:03:37 PM:     at /opt/build/repo/node_modules/gulp/bin/gulp.js:129:20
10:03:37 PM:     at _combinedTickCallback (internal/process/next_tick.js:132:7)

I have compared the code from the 2 repositories (cloned and new) and it's 100% the same.
The clone is found here: https://github.com/DotTech/one-click-hugo-cms
The created repo here: https://github.com/DotTech/hugo-test

Googling for the spawn EACCES error didn't give me any results (at least not in the context of Netlify or Hugo).
Hope that someone here can point me in the right direction?

The "solution" for now is to just clone the repository and continue to work on that, but I would like to start fresh with one single commit and not have all the history.

No media loading and uploading for Deploy to Netlify

I found the problem with no pictures shown in Media and unable to upload them, too.

I have used the Deploy to Netlify button to try it.

It is the same issue as closed decaporg/decap-cms#1565 or closed decaporg/decap-cms#1608, so it seems to me that it is solved generally, but not for the one-click example?

Include working example of hugos image porcessing with netlify

Hugo has powerful image processing capabilities built in, however they are limited to a “Page Bundle” layout, where your images live in the same folder as the content that is referencing them. NetlifyCMS does not (yet?) support this layout.
Instead, all images are stored in one folder under /static.

It is possible to make netlify and Hugo image processing work together by moving the image folder inside of content and making it a “headless” (non-rendered) section. Access can be provided via partials.

I got this to work after a lot of trail and error and I am not exactly sure if I am doing it the best way.

Building an example into this template could probably spare people a lot of experimentation.

Writing sass

Is there a way to write sass and compile it in one-click-hugo-cms? What is the location for sass folder? Any docs concerning using sass instead of css would be highly appreciated. Thank you.

Dependencies need to be updated

Quite a few warnings, including some scary ones:

npm WARN deprecated [email protected]: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated [email protected]: express 2.x series is deprecated
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: connect 1.x series is deprecated
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.

And the node-sass release has gone away ..

[email protected] install /home/john/repos/git/one-click-hugo-cms/node_modules/node-sass
node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v3.13.1/linux-x64-57_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v3.13.1/linux-x64-57_binding.node":

HTTP error 404 Not Found

Dependency deprecation warning: gulp-util (npm)

On registry https://registry.npmjs.org/, the "latest" version (v3.0.8) of dependency gulp-util has the following deprecation notice:

gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about gulp-util's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

Adds maintenance tooling

Summary

To make sure that our project stays up to date we'd like to add some tools:

• Cypress integration (for testing e2e, ref doc here)
• Renovate (for dependency management)
  add 'renovate.json` to project root

  {
    "$schema": "https://docs.renovatebot.com/renovate-schema.json",
    "extends": [
      "local>netlify-templates/renovate-config"
    ]
  }
  

• Disable dependabot secutrity and version update alerts
• Make sure to update the README on how to remove everything
  • add section on cypress removal
  • add section on removing renovate json file
  • add comment at top of renovate json saying it can be removed if not using renovate

Double </body></html> tags on every page

(Noob here) I removed the tags from the bottom of this file and that seemed to fix the issue...

404 for app.js

- Do you want to request a feature or report a bug?
Report a bug

- What is the current behavior?
There's a reference to app.js that is generating a 404

- If the current behavior is a bug, please provide the steps to reproduce.
Deploy https://github.com/netlify-templates/one-click-hugo-cms to Netlify
Access the homepage
the bottom of the homepage source contains the following HTML

<script src="/app.js"></script>
but that file generates a 404

See fresh deploy here
https://quizzical-aryabhata-bec172.netlify.com/
this is the file it tries to load
https://quizzical-aryabhata-bec172.netlify.com/app.js

- What is the expected behavior?
Either the reference should not be there or the file should be.
There is an app.js in the git repo, I presume this is what should be in the dist folder
https://github.com/netlify-templates/one-click-hugo-cms/blob/master/src/js/app.js

- Please mention your node.js, NPM, Hugo and operating system version.
Just deployed https://github.com/netlify-templates/one-click-hugo-cms to Netlify

Preview does not show image rendering

Just quickly tried it out and that was my first impression. Why is that? It's jarring.

Document custom fork of styling?

Hi all,

Been enjoying using this template as a starting point. Could there be an explanation of why the choice was made to go with a custom fork of Tachyons and/or PostCSS, what the differences are, and how to best account for that if we want to update Tachyons or use other tooling on the css side of things?

Blank /admin page after pull from master

I've done a pull from master attempting to fix the vulnerabilities issues highlighted by GitHub (as per https://community.netlify.com/t/yarn-lock-vulnerabilities-found-in-default-hugo-netlify-cms-site/2016).

I've sorted the merge conflicts and pushed the changes to my repo and then Netlify deployed successfully.

The website looks alright and GitHub is happy but the /admin page is white (although it read the Content Manager title). I've already tried in Incognito Mode.

Any thoughts, something I missed?

Build and start issues (maybe sass related)

- Do you want to request a feature or report a bug?
Bug

- What is the current behavior?

Running yarn or npm install on a fresh clone fails during the node-sass build.

yarn install v1.22.15
[1/4] Resolving packages...
[2/4] Fetching packages...
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "netlify-cms-app > netlify-cms-core > [email protected]" has unmet peer dependency "@types/react@>=16".
warning "netlify-cms-app > netlify-cms-widget-colorstring > [email protected]" has incorrect peer dependency "react@^17.0.1".
warning "netlify-cms-app > netlify-cms-widget-colorstring > [email protected]" has incorrect peer dependency "react-dom@^17.0.1".
warning "netlify-cms-app > netlify-cms-core > redux-notifications > [email protected]" has incorrect peer dependency "redux@^2.0.0 || ^3.0.0".
[4/4] Building fresh packages...
[1/2] ⠈ hugo-bin
error /home/nilueps/Sync/one-click-hugo-cms/node_modules/node-sass: Command failed.
Exit code: 1
Command: node scripts/build.js
Arguments:
Directory: /home/nilueps/Sync/one-click-hugo-cms/node_modules/node-sass
Output:
Building: /usr/bin/node /home/nilueps/Sync/one-click-hugo-cms/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [
gyp verb cli   '/usr/bin/node',
gyp verb cli   '/home/nilueps/Sync/one-click-hugo-cms/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library='
gyp verb cli ]
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "/usr/bin/python" in the PATH
gyp verb `which` succeeded /usr/bin/python /usr/bin/python
gyp ERR! configure error
gyp ERR! stack Error: Command failed: /usr/bin/python -c import sys; print "%s.%s.%s" % sys.version_info[:3];
gyp ERR! stack   File "<string>", line 1
gyp ERR! stack     import sys; print "%s.%s.%s" % sys.version_info[:3];
gyp ERR! stack                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
gyp ERR! stack SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
gyp ERR! stack
gyp ERR! stack     at ChildProcess.exithandler (node:child_process:397:12)
gyp ERR! stack     at ChildProcess.emit (node:events:390:28)
gyp ERR! stack     at maybeClose (node:internal/child_process:1064:16)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
gyp ERR! System Linux 5.15.16-200.fc35.x86_64
gyp ERR! command "/usr/bin/node" "/home/nilueps/Sync/one-click-hugo-cms/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /home/nilueps/Sync/one-click-hugo-cms/node_modules/node-sass
gyp ERR! node -v v16.13.2
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1

I managed to solve this first problem by instructing npm to use python 2 instead of 3: npm config set python $(which python2).

But then I am hit with some node-sass related build errors: log

Removing the deprecated node-sass and replacing it with the sass packages fixes that problem; but then yarn start fails to transpile the css properly.

I tried the same steps with yarn 1.22.15 and 3.1.1 as well as with npm 8.4.1.
My node version is 16.13.2
I'm using Fedora 34 with kernel 5.15.16

Having a tough time getting one-click-hugo-cms running locally.

Having a tough time getting one-click-hugo-cms running locally.

(Maybe these issues stem from victor/hugo itself rather than this project?)

System
Win7 64bit
node -v 8.9.1
npm -v 5.0.3

Installing in both cmd and bash

npm WARN deprecated [email protected]: �  Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN [email protected] requires a peer of react@^15.6.2 but none was installed.
npm WARN [email protected] requires a peer of react-transition-group@^1.1.3 but none was installed.
npm WARN [email protected] requires a peer of slate@^0.23.0 but none was installed.
npm WARN [email protected] requires a peer of slate@^0.26.1 but none was installed.
npm WARN [email protected] requires a peer of slate@^0.28.2 but none was installed.
npm WARN [email protected] requires a peer of slate@^0.26.1 but none was installed.
npm WARN [email protected] No repository field.

npm ERR! Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped?

Ignoring the warnings and running npm start

[11:46:51] Failed to load external module babel-register
[11:46:51] Failed to load external module babel-core/register
[11:46:51] Failed to load external module babel/register
[11:46:51] Local gulp not found in ~\test_netlifycms\one-click-hugo-cms
[11:46:51] Try running: npm install gulp
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `gulp server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\jaegz\AppData\Roaming\npm-cache\_logs\2017-11-15T16_46_51_947Z-debug.log

Deleting the node_modules folder, updating package.json packages to the latest versions, and running npm install again

npm WARN deprecated [email protected]: �  Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN [email protected] No repository field.

Ignoring the warnings and running npm start again

[11:50:47] Failed to load external module babel-register
[11:50:47] Failed to load external module babel-core/register
[11:50:47] Failed to load external module babel/register
[11:50:47] Local gulp not found in ~\test_netlifycms\one-click-hugo-cms
[11:50:47] Try running: npm install gulp
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `gulp server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\jaegz\AppData\Roaming\npm-cache\_logs\2017-11-15T16_50_47_083Z-debug.log

Debug log (2017-11-15T16_50_47_083Z-debug.log)

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Users\\jaegz\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 silly lifecycle [email protected]~prestart: no script for prestart, continuing
7 info lifecycle [email protected]~start: [email protected]
8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~start: PATH: C:\Users\jaegz\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\Users\jaegz\test_netlifycms\one-click-hugo-cms\node_modules\.bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\jaegz\bin;C:\Users\jaegz\Downloads\cmder\bin;C:\Users\jaegz\Downloads\cmder\vendor\conemu-maximus5\ConEmu\Scripts;C:\Users\jaegz\Downloads\cmder\vendor\conemu-maximus5;C:\Users\jaegz\Downloads\cmder\vendor\conemu-maximus5\ConEmu;C:\Program Files (x86)\RSA SecurID Token Common;C:\Program Files\RSA SecurID Token Common;C:\Windows\System32;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Common Files\Lenovo;C:\SWTOOLS\ReadyApps;C:\Ruby193\bin;C:\Program Files\Intel\WiFi\bin;C:\Program Files\Common Files\Intel\WirelessCommon;C:\Program Files (x86)\WebEx\Productivity Tools;C:\Program Files\Amazon\AWSCLI;C:\Go\bin;C:\Users\jaegz\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Program Files\Git\cmd;C:\php;C:\curl;C:\Program Files\nodejs;C:\Program Files (x86)\Yarn\bin;C:\Windows\System32;C:\Program Files\Intel\WiFi\bin;C:\Program Files\Common Files\Intel\WirelessCommon;C:\Python34;C:\Python34\Scripts;C:\Users\jaegz\AppData\Roaming\Python\Scripts;C:\Hugo\bin;C:\Users\jaegz\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Program Files\Microsoft VS Code\bin;C:\Users\jaegz\AppData\Roaming\npm;C:\Users\jaegz\bash-scripts;C:\Users\jaegz\AppData\Local\Yarn\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\share\vim\vim74;C:\Users\jaegz\Downloads\cmder
10 verbose lifecycle [email protected]~start: CWD: C:\Users\jaegz\test_netlifycms\one-click-hugo-cms
11 silly lifecycle [email protected]~start: Args: [ '/d /s /c', 'gulp server' ]
12 silly lifecycle [email protected]~start: Returned: code: 1  signal: null
13 info lifecycle [email protected]~start: Failed to exec start script
14 verbose stack Error: [email protected] start: `gulp server`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (C:\Users\jaegz\AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:283:16)
14 verbose stack     at emitTwo (events.js:126:13)
14 verbose stack     at EventEmitter.emit (events.js:214:7)
14 verbose stack     at ChildProcess.<anonymous> (C:\Users\jaegz\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:126:13)
14 verbose stack     at ChildProcess.emit (events.js:214:7)
14 verbose stack     at maybeClose (internal/child_process.js:925:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
15 verbose pkgid [email protected]
16 verbose cwd C:\Users\jaegz\test_netlifycms\one-click-hugo-cms
17 verbose Windows_NT 6.1.7601
18 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\jaegz\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
19 verbose node v8.9.1
20 verbose npm  v5.0.3
21 error code ELIFECYCLE
22 error errno 1
23 error [email protected] start: `gulp server`
23 error Exit status 1
24 error Failed at the [email protected] start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]

npm install gulp --save & npm start

> [email protected] start C:\Users\jaegz\test_netlifycms\one-click-hugo-cms
> gulp server

[12:21:19] Failed to load external module babel-register
[12:21:19] Failed to load external module babel-core/register
[12:21:19] Failed to load external module babel/register
C:\Users\jaegz\test_netlifycms\one-click-hugo-cms\gulpfile.babel.js:1
(function (exports, require, module, __filename, __dirname) { import gulp from "gulp";
                                                              ^^^^^^

SyntaxError: Unexpected token import
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:139:10)
    at Module._compile (module.js:599:28)
    at Object.Module._extensions..js (module.js:646:10)
    at Module.load (module.js:554:32)
    at tryModuleLoad (module.js:497:12)
    at Function.Module._load (module.js:489:3)
    at Module.require (module.js:579:17)
    at require (internal/module.js:11:18)
    at Liftoff.handleArguments (C:\Users\jaegz\test_netlifycms\one-click-hugo-cms\node_modules\gulp\bin\gulp.js:116:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `gulp server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\jaegz\AppData\Roaming\npm-cache\_logs\2017-11-15T17_21_19_166Z-debug.log

Looks like babel and the config files are out of sync since import throws a syntax error?

Why is there no "New page" button?

In the admin panel you can add or edit posts, and you can edit pages, but not add new pages, how come?

Error when starting with micromatch package

The following error appears when I npm start:

C:\Users\Jonas\Desktop\test\one-click-hugo-cms [master ≡]> npm start    

> [email protected] start C:\Users\Jonas\Desktop\test\one-click-hugo-cms
> gulp server   

[17:00:43] Failed to load external module @babel/register
[17:00:43] Requiring external module babel-register
C:\Users\Jonas\Desktop\test\one-click-hugo-cms\node_modules\micromatch\index.js:44
    let isMatch = picomatch(String(patterns[i]), { ...options, onResult }, true);
                                                   ^^^
SyntaxError: Unexpected token ...
    at createScript (vm.js:53:10)
    at Object.runInThisContext (vm.js:95:10)
    at Module._compile (module.js:543:28)
    at Module._extensions..js (module.js:580:10)
    at Object.require.extensions.(anonymous function) [as .js] (C:\Users\Jonas\Desktop\test\one-click-hugo-cms\node_modules\babel-register\lib\node.js:152:7)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)   

npm ERR! Windows_NT 10.0.17763
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
npm ERR! node v7.7.2
npm ERR! npm  v4.1.2
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: `gulp server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script 'gulp server'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the victor-hugo package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp server
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs victor-hugo
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls victor-hugo
npm ERR! There is likely additional logging output above.   

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\Jonas\Desktop\test\one-click-hugo-cms\npm-debug.log

Steps to reproduce

1. git clone the repo
2. npm install
3. npm start
4. Get the error

The micromatch version throwing the error is 4.0.2. What packages require it:

+-- [email protected]
| +-- [email protected]
| | +-- [email protected]
| | | `-- [email protected]
| | `-- [email protected]
| |   `-- [email protected]
| `-- [email protected]
+-- [email protected]
| `-- [email protected]
|   `-- [email protected]
|     `-- [email protected]
+-- [email protected]
| `-- [email protected]
|   `-- [email protected]
`-- UNMET PEER DEPENDENCY [email protected]    

npm ERR! peer dep missing: webpack@^4.0.0, required by [email protected]

Applying markdown to Pages

Re:
#103 (comment)

I've tried to apply the markdown widget to pages so hyperlinks and paragraph formatting can be added to Pages. The markdown editing pane now appears in the CMS. But adding hyperlinks to text causes actual markdown to appear in the live page, and no hyperlinks appear. (Same with line breaks, paragraph tags.)

Is this use of widget:"markdown" incorrect? (config.yml) Thanks!

       - {label: "Blurb", name: blurb, widget: object, fields: [
          {label: "Heading", name: "heading", widget: string},
          {label: "Text", name: "text", widget: "markdown"}]}
      - {label: "Intro", name: intro, widget: object, fields: [
          {label: "Heading", name: "heading", widget: string},
          {label: "Text", name: "text", widget: "markdown"}]}
      - {label: "Products", name: products, widget: list, fields: [
          {label: "Image", name: "image", widget: "image"},
          {label: "Text", name: "text", widget: "markdown"}]}

Still redirecting to /admin while logged into the CMS

I am noticing that while I am logged into the CMS, I cannot view the homepage and get redirected back to "/admin". I see this commit ab57ad3b7547089eee9a2fb4484c370ef6730c2a should solve this issue, but that is not the case on the site I just cloned from this template: https://cook-doris-42316.netlify.com

I have to log out to view the homepage

Local development problem

ran npm install and now running npm start gives this message

[13:56:59] Requiring external module babel-register
Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more, see https://fb.me/prop-types-docs
Warning: Accessing createClass via the main React package is deprecated, and will be removed in React v16.0. Use a plain JavaScript class instead. If you're not yet ready to migrate, create-react-class v15.* is available on npm as a temporary, drop-in replacement. For more info see https://fb.me/react-create-class
/Users/devionvillegas/Documents/GitHub/one-click-hugo-cms/node_modules/core-js/library/fn/json/stringify.js:4
return $JSON.stringify.apply($JSON, arguments);
^

TypeError: Converting circular structure to JSON
at Object.stringify ()
at stringify (/Users/devionvillegas/Documents/GitHub/one-click-hugo-cms/node_modules/core-js/library/fn/json/stringify.js:4:26)
at compile (/Users/devionvillegas/Documents/GitHub/one-click-hugo-cms/node_modules/babel-register/lib/node.js:105:42)
at loader (/Users/devionvillegas/Documents/GitHub/one-click-hugo-cms/node_modules/babel-register/lib/node.js:144:14)
at Object.require.extensions.(anonymous function) [as .js] (/Users/devionvillegas/Documents/GitHub/one-click-hugo-cms/node_modules/babel-register/lib/node.js:154:7)
at Module.load (module.js:545:32)
at tryModuleLoad (module.js:508:12)
at Function.Module._load (module.js:500:3)
at Module.require (module.js:568:17)
at require (internal/module.js:11:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: gulp server
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Editing the Template Title

hi,

When I post a link of my website (based on one-click-hugo-cms) on Twitter, it still shows Kaldi | Coffee with a Conscience.

How do I remove it?

Thank You

Where do we edit the CSS?

The admin page is really helpful but have not been successful finding the CSS responsible for the layout.

The left panel shows the paragraphs nicely divided but when it appears on the actual site, it becomes a big lump of words.

Thanks.

formatting the css within paragraphs

Am using the Netlify CMS which allows editing of the One-Click-Hugo-CMS with ease.

Am writing to find out if the issue is with the Netlify CMS or the One-Click-Hugo-cms that's messing with the formatting.

eg. in this page https://www.speechtherapyworks.com.sg/values/ you can see the profile of the director but it appears a one long paragraph. But on the file it's already using markdown format. So either the Netlify CMS or the One-Click-Hugo-cms is "overiding" the formatting and only recognizing it as "

"

How should I trouble shoot to get the formatting done correctly?

Feature request: Hamburger menu

Current menu does not seem to resize properly on smartphones. (See: https://master-template-one-click-hugo-cms.netlify.com/ )

[Guide] Gulpfile chages required to use with gulp 4.0.0

I recently updated to gulp 4 in one of my projects using one-click-hugo-cms. Here is my gulpfile.babel.js. It is working from my testing.

const { src, dest, series, watch } = require('gulp');
const cp = require("child_process");
const gutil = require("gulp-util");
const postcss = require("gulp-postcss");
const cssImport = require("postcss-import");
const cssnext = require("postcss-cssnext");
const BrowserSync = require("browser-sync");
const webpack = require("webpack");
const webpackConfig = require("./webpack.conf");
const svgstore = require("gulp-svgstore");
const svgmin = require("gulp-svgmin");
const inject = require("gulp-inject");
const cssnano = require("cssnano");

const browserSync = BrowserSync.create();
const hugoBin = `./bin/hugo.${process.platform === "win32" ? "exe" : process.platform}`;
const defaultArgs = ["-d", "../dist", "-s", "site"];

if (process.env.DEBUG) {
  defaultArgs.unshift("--debug");
}

function hugo(cb) {
  buildSite(cb)
}

function hugoPreview(cb) { 
  buildSite(cb, ["--buildDrafts", "--buildFuture"])
}

function build(cb) {
  return series(css, js, hugo)(cb);
}

function buildPreview(cb) {
  return series(css, js, hugoPreview)(cb);
}

function css() {
  return src("./src/css/*.css")
    .pipe(postcss([
      cssImport({from: "./src/css/main.css"}),
      cssnext(),
      cssnano(),
    ]))
    .pipe(dest("./dist/css"))
    .pipe(browserSync.stream());
}

function js(cb) {
  const myConfig = Object.assign({}, webpackConfig);

  webpack(myConfig, (err, stats) => {
    if (err) throw new gutil.PluginError("webpack", err);
    gutil.log("[webpack]", stats.toString({
      colors: true,
      progress: true
    }));
    browserSync.reload();
    cb();
  });
}

function svg() {
  const svgs = src("site/static/img/icons-*.svg")
    .pipe(svgmin())
    .pipe(svgstore({inlineSvg: true}));

  function fileContents(filePath, file) {
    return file.contents.toString();
  }

  return src("site/layouts/partials/svg.html")
    .pipe(inject(svgs, {transform: fileContents}))
    .pipe(dest("site/layouts/partials/"));
}

function server() {
  build();
  browserSync.init({
    server: {
      baseDir: "./dist"
    }
  });
  watch("./src/js/**/*.js", js);
  watch("./src/css/**/*.css", css);
  watch("./site/static/img/icons-*.svg", svg);
  watch("./site/**/*", hugo);
}

function buildSite(cb, options) {
  const args = options ? defaultArgs.concat(options) : defaultArgs;

  return cp.spawn(hugoBin, args, {stdio: "inherit"}).on("close", (code) => {
    if (code === 0) {
      browserSync.reload("notify:false");
      cb();
    } else {
      browserSync.notify("Hugo build failed :(");
      cb("Hugo build failed");
    }
  });
}

exports.hugo = hugo;
exports.start = server;
exports.build = build;
exports.webpack = js;
exports.preview = buildPreview;

Need to change the build-preview script in package.json a little bit.

"build-preview": "gulp build-preview",

Change to

"build-preview": "gulp preview",

Let me know if I missed something. We can try and improve it together

Trying to change the orange colour

Hello I am trying to change the orange color on the template on my website for #71c4f7 (light blue). I have changed it in the _variables.css and it isn't working. Any help?

Website: https://www.kewls.net/
Github Repo: https://github.com/bwhybrow23/kewl-website

Image preview on Value page not working

I have deployed this repo to netlify without any problem. Admin works too.

But I have noticed something weird
Steps to reproduce:
Go to admin and click Value page to edit the page. (All the images are there in the preview)
Change the image of the first value and now the image of this first value is gone from the preview pane although it's still there in the edit pane.

I've run this locally and it's exactly like that too: I changed the image of the first value and now that image is gone from the preview pane, the other images are still there.

I've played around with src/js/cms-preview-templates/value.js but I am totally lost here.

Any help would be greatly appreciated. Thank you.

SVG processing does not match documentation

- Do you want to request a feature or report a bug?
What I think is a bug or at least inaccuracy in the docs

- What is the current behavior?
In the SVG section od https://github.com/netlify-templates/one-click-hugo-cms/blob/master/README.md it says:

1/
automatically optimized with SVGO (gulp-svgmin)

2/
concatenated into a single SVG sprite stored as a a partial called svg.html

I don't think either of these things are happening.

- If the current behavior is a bug, please provide the steps to reproduce.

Add a new icon (e.g. icons-whatsapp.zip ) to site\static\img and neither of the above steps seems to happen

- What is the expected behavior?

A previous version used to have a build command that would merge/overlay site\static\img\icon.svg with each of site\static\img\icons-* and create the SVG snippet that could be inserted into site\layouts\partials\svg.html

I think the docs should be updated to reflect what is happening or vice versa.

- Please mention your node.js, NPM, Hugo and operating system version.

Netlify Identity widget is loaded on every page (160kb)

Is it really necessary to load the Netlify Identity widget on every page? Currently, it's a blocking 160kb in the head section.

<script src="https://identity.netlify.com/v1/netlify-identity-widget.js"></script>

See https://github.com/netlify-templates/one-click-hugo-cms/blob/master/site/layouts/partials/head.html#L26

I don't quite understand:

• Where do we really need it? Would the /admin/ page be sufficient?
• Could we do an async load instead?

Dependency deprecation warning: babel-preset-es2015 (npm)

On registry https://registry.npmjs.org/, the "latest" version (v6.24.1) of dependency babel-preset-es2015 has the following deprecation notice:

🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about babel-preset-es2015's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

Incompatible with theme?

I am not the greatest code developer, which means I rely on tutorials and documentation heavily. I tried to setup this with the theme hugo-icon. Following this victor hugo theme guide (the only one I can find), I setup a site and the admin sub directory seems to not be working. Whenever I open subdomain.nelify.com/admin, it gives a netlify loading icon and goes away, see for yourself on the site.

I do not know what I have done wrong and I followed the guide exactly and setup the password from the email. Help me out and lead me to any documentation if you can on how victor hugo works aswell please, thank you!

Use baseof and pagination

Hugo has had a tonne of updates. It would be nice to see this template using baseof, pagination and shortcodes which would make the layouts a more manageable especially for those less familiar with Hugo.

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• Update babel monorepo to v7.21.4 (@babel/core, @babel/preset-env)
• Update dependency eslint to v8.37.0
• Update dependency hugo-bin to ^0.102.0
• Update dependency immutable to v4.3.0
• Update dependency sass to v1.60.0
• Update dependency webpack to v5.77.0
• Update dependency webpack-dev-server to v4.13.2
• Update Node.js to v18
• Update dependency babel-loader to v9
• Update dependency css-minimizer-webpack-plugin to v5
• Update dependency cypress to v12
• Update dependency postcss-custom-media to v9
• Update dependency postcss-import to v15
• Update dependency postcss-loader to v7
• Update dependency postcss-preset-env to v8
• Update dependency sass-loader to v13
• Update dependency webpack-cli to v5

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• Update react monorepo to v18 (major) (react, react-dom)

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency copy-webpack-plugin to v11
• Update dependency exports-loader to v4
• Update dependency imports-loader to v4
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

npm

package.json

• @babel/preset-react ^7.17.12
• cypress ^10.5.0
• date-fns ^2.28.0
• immutable ^4.1.0
• netlify-cms-app ^2.15.72
• netlify-plugin-cypress ^2.2.1
• react ^17.0.2
• react-dom ^17.0.2
• to-string-loader ^1.2.0
• @babel/core ^7.16.0
• @babel/eslint-parser ^7.16.3
• @babel/preset-env ^7.16.0
• @babel/register ^7.16.0
• assets-webpack-plugin ^7.1.1
• autoprefixer ^10.4.7
• babel-loader ^8.2.3
• clean-webpack-plugin ^4.0.0
• copy-webpack-plugin ^9.1.0
• cross-env ^7.0.3
• css-loader ^6.5.1
• css-minimizer-webpack-plugin ^4.0.0
• eslint ^8.2.0
• eslint-plugin-import ^2.26.0
• exports-loader ^3.1.0
• file-loader ^6.2.0
• html-webpack-plugin ^5.5.0
• hugo-bin ^0.98.0
• imports-loader ^3.1.1
• mini-css-extract-plugin ^2.4.4
• npm-run-all ^4.1.5
• postcss ^8.3.11
• postcss-custom-media ^8.0.2
• postcss-import ^14.0.2
• postcss-loader ^6.2.0
• postcss-preset-env ^7.7.2
• sass ^1.53.0
• sass-loader ^12.3.0
• style-loader ^3.3.1
• terser-webpack-plugin ^5.2.5
• webpack ^5.64.1
• webpack-cli ^4.9.1
• webpack-dev-server ^4.5.0
• webpack-merge ^5.8.0

nvm

.nvmrc

• node 16

---

• Check this box to trigger a request for Renovate to run again on this repository

can this framework be used locally to generate /public folder to be deployed elsewhere?

i want to use this cms locally to generate the /public folder that will be deployed in my website custom domain.

i'm not able to understand how to do this.

i can locally run the cms connecting to netlify account; but instead i want to run locally the cms only to easily manage content generation.

is this possible?

thanks.

Dependency deprecation warning: postcss-cssnext (npm)

On registry https://registry.npmjs.org, the "latest" version (v3.1.0) of dependency postcss-cssnext has the following deprecation notice:

'postcss-cssnext' has been deprecated in favor of 'postcss-preset-env'. Read more at https://moox.io/blog/deprecating-cssnext/

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about postcss-cssnext's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]