anshul137 / ag-ssg

Static Site Generator

Hey! Everyone

Welcome to my page!

Badge Board

ag-ssg's Issues

Support for a horizontal rule in Markdown.

• Adding the support for Markdown Feature.
• The Markdown --- should get converted to an

  ---

  tag

Add an option-l, --lang flag, which indicates the language to use when generating the lang attribute on

Description:
In my ag-ssg
I am adding the new feature for the language support
where user can input the command such as node app.js - l
which indicates the language to use when generating the lang attribute on the html page.

Add config support

The configuration always makes it easier to use the tool, especially if you do it frequently and don't want to write a colossal command every time. I want to implement the functionality that would add the --config flag and use the config.json to configure the tool

Error when attempting to use `--input` flag

When attempting to execute the program with the --input flag on the CLI, an error message is returned and no output HTML files are generated.

Attempted command:

PS C:\Users\<username>\Documents\School\DPS909\Asn\A1\ag-ssg> node app.js -i "textfile\Silver Blaze.txt"

Resulting output:

Version details: 0.1
Name of the package:ssg
input:textfile\Silver Blaze.txt
file:///C:/Users/username/Documents/School/DPS909/Asn/A1/ag-ssg/index.js:24
    fs.rm(dir, { recursive: true });
       ^

TypeError: fs.rm is not a function
    at ssg_ (file:///C:/Users/username/Documents/School/DPS909/Asn/A1/ag-ssg/index.js:24:8)
    at file:///C:/Users/username/Documents/School/DPS909/Asn/A1/ag-ssg/app.js:33:3
    at ModuleJob.run (internal/modules/esm/module_job.js:138:23)
    at async Loader.import (internal/modules/esm/loader.js:178:24)
PS C:\Users\username\Documents\School\DPS909\Asn\A1\ag-ssg>

Addition of initial Markdown support

I'd like to add to your code so that it can parse .md files and output appropriate HTML based on the Markdown format.

I intend to add support for the # header1 and ## header2 syntax features, such that if a line of texts begins with '#' or '##', it will be placed inside an <h1> or <h2> element, respectively, rather than a <p> element.

This should only entail some minor edits to your writeFile(filename, data) function.

App is breaking

app is breaking generating lot of errors

README.md file - minor errors

A few minor spelling errors are present in the README.md file.

Also, I think some of the instructions could be a little clearer — for example, the "clone repos into your local drive" segment uses the 'git clone' command like "git clone <project_name>". The argument referred to as "<project_name>" actually denotes the exact file-path of where the cloned-repos will be saved.
So I think the instructions should state that.

Additionally, the README.md file doesn't state which modules are in the list of dependencies for the program.

Version number in `package.json` is an invalid number

Version number in package.json is listed as 0.1.
Version number should be in the format x.x.x. I recommend using 0.1.0.

Help message in CLI help flag is minimal

The help message printed to the console by the --help flag only prints the program name, version number and "help:true".
I take this as a placeholder help message. Just a reminder to update it.

Attempting to run `npm link` on the CLI gives an error

Attempting to run npm link in the terminal gives the following output, with the version number set to 0.1 in package.json:

npm ERR! Invalid version: "0.1"

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\<username>\AppData\Roaming\npm-cache\_logs\2022-09-16T22_41_46_230Z-debug.log

I tried changing the version number to "0.1.0", which resolved the "invalid version number" error. However, found 7 vulnerabilities were found when attempting to run npm link afterwards with the valid version number.

Here is the terminal's output with the version number set to 0.1.0 in package.json:

npm WARN [email protected] No repository field.

audited 241 packages in 1.089s

10 packages are looking for funding
  run `npm fund` for details       

found 7 vulnerabilities (2 low, 2 moderate, 2 high, 1 critical)
  run `npm audit fix` to fix them, or `npm audit` for details
npm ERR! code ENOENT
npm ERR! syscall chmod
npm ERR! path C:\Users\<username>\AppData\Roaming\npm\node_modules\agandhi29_static_site_geneator\main.js
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, chmod 'C:\Users\<username>\AppData\Roaming\npm\node_modules\agandhi29_static_site_geneator\main.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\<username>\AppData\Roaming\npm-cache\_logs\2022-09-16T22_47_40_708Z-debug.log

Add the Theme Feature to the application

Prototype
Planned to use the Darkmode.js so that users can switch from light to dark mode according to their preference.
Default will be according to the system theme.