I removed the "type": "module" from the packge.json file as your instructed and ran the npm run build command. I now receive the following error:
> keenthemes@1.0.0 build
> webpack
>> Building...
node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^
[Error: EPERM: operation not permitted, rmdir 'C:\DEVELOPMENT\RD\django_demo1\starterkit\assets\css'] {
errno: -4048,
code: 'EPERM',
syscall: 'rmdir',
path: 'C:\\django_demo1\\starterkit\\assets\\css'
}
Node.js v20.0.0
Use your file explorer or a command-line tool to delete the 'css' directory located at 'C:\DEVELOPMENT\RD\django_demo1\starterkit\assets\css'. Tomb of the Mask
Hi Lexim,
In the starter kit, only a limited number of pages are included for demonstration purposes. However, you have the option to add more pages by referring to the HTML version of Metronic. The styles required for these additional pages are already included in the starter kit, so you don't need to worry about that.
To add more pages, you can navigate to the HTML version of Metronic and select the desired page you want to incorporate into your project. Copy the relevant HTML code and create a new page in your application. Paste the copied HTML code into the new page and make any necessary adjustments or customizations.
Thanks
Hi Lexim,
The error message indicates that the build process encountered a permission issue while trying to remove the 'C:\DEVELOPMENT\RD\django_demo1\starterkit\assets\css' directory. The operation is not permitted, possibly due to insufficient permissions or a conflicting process locking the directory.
To resolve this issue, you can try the following steps:
1. Check if any other processes or programs are using the 'C:\DEVELOPMENT\RD\django_demo1\starterkit\assets\' directory or its contents. Close any applications or terminals that might be accessing the files.
2. If you are using an integrated development environment (IDE) or a code editor, try closing and reopening it. Sometimes, IDEs hold onto file handles, causing permission conflicts.
3. Restart your computer to release any locked resources and clear any conflicting processes.
After performing these steps, try running the 'npm run build' command again and check if the issue is resolved. If the problem persists, please let us know.
Thanks
This problem was solved, but now none of the pages other than the home page load. For example, if I click on Dashboard -> eCommerge -- nothing happens. The link at the bottom of the browser shows http://127.0.0.01:8000/# for any of the links except the links under the Help menu.