millenniumearl / f95api Goto Github PK

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.

Location: renovate.json
Error type: Invalid JSON (parsing failed)
Message: Syntax error: expecting String near ], sched

Description

Trailing commas in object literals are valid according to the ECMAScript 5 (and ECMAScript 3!) spec. However, IE8 (when not in IE8 document mode) and below will throw an error when it encounters trailing commas in JavaScript. var foo = { bar: "baz", qux: "quux", }; Trailing commas …

Occurrences

There are 21 occurrences of this issue in the repository.

See all occurrences on DeepSource → deepsource.io/gh/MillenniumEarl/F95API/issue/JS-0134/occurrences/

Describe the bug
Games with "Completed" tags are marked as "Ongoing"

To Reproduce
Steps to reproduce the behavior:

1. Search a game with name
2. Check status property

Additional context
Some games where the bug is confirmed:

• https://f95zone.to/threads/acting-lessons-v1-0-2-drpinkcake.12181/
• https://f95zone.to/threads/below-sunshade-v2-0-2-bugfix-arvus-games.39624/
• https://f95zone.to/threads/ciri-trainer-ch-5-v1-0-beta-the-worst.18795/

Describe the bug
The use of Dark Mode BETA Theme prevents the use of F95API as one of the two ld+json script tags is not present in the HTML source of the thread's pages. In particular is missing the script containing "@type":"DiscussionForumPosting",

To Reproduce
Steps to reproduce the behavior:

1. Change the theme from White theme/UI.X.Dark to Dark Mode BETA
2. Use the module to search for a thread
3. Expect an error at utils > getDateFromString line 16 because s is undefined.

Expected behavior
There should be no usage differences based on the theme chosen by the user.

Additional context
Since the problem is with the site, a report has been opened on the site at this address.

Describe the bug
On threads with an old template it is not possible to obtain information on the release date or overview because different keywords are used, such as "Story" instead of "Overview" and "Updated" instead of "Release date".

It is also recommended to use Regex in the release dates to get the dates if they are mixed with other information (see example).

Additional context
Some sites where the reported problems occur:

• https://f95zone.to/threads/the-winds-disciple-pixel-games.447/
• https://f95zone.to/threads/euphoria-final-clock-up.638/

I see this when running the example with the correct credentials. I can confirm that this worked a few days ago when was testing #257. Pretty sure this is caused by the newly added DDOS protection from DDOS-GUARD. Need to debug this further and probably look into bypassing DDOS-GUARD (could be something custom or a lib).

f95api: v2.0.0-beta.12
Node.js: v17.6.0
Windows 10: v19044.1586

PS G:\dev\code\F95API> npm run example

> @millenniumearl/[email protected] example     
> npm run build && node --inspect ./dist/example.js


> @millenniumearl/[email protected] prebuild
> node -p "'export const LIB_VERSION = ' + JSON.stringify(require('./package.json').version) + ';'" > src/version.ts


> @millenniumearl/[email protected] build
> npm run prebuild && tsc --project ./      


> @millenniumearl/[email protected] prebuild
> node -p "'export const LIB_VERSION = ' + JSON.stringify(require('./package.json').version) + ';'" > src/version.ts

Debugger listening on ws://127.0.0.1:9229/cedbfbf7-6837-4df6-ba8e-3fb0e50b85d3
For help, see: https://nodejs.org/en/docs/inspector
Authenticating...
G:\dev\code\F95API\dist\scripts\network-helper.js:111
        throw new errors_1.InvalidF95Token(`Invalid token for auth: ${credentials.token}`);
              ^

InvalidF95Token [Error]: Invalid token for auth: undefined
    at authenticate (G:\dev\code\F95API\dist\scripts\network-helper.js:111:15)        
    at loginInTheRemotePlatform (G:\dev\code\F95API\dist\scripts\login.js:105:58)     
    at login (G:\dev\code\F95API\dist\scripts\login.js:47:29)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async authenticate (G:\dev\code\F95API\dist\example.js:72:20)
    at async main (G:\dev\code\F95API\dist\example.js:143:9)

Describe the bug
Older games that are described on threads using a different template than the current one have an undefined version field. This can be caused by the fact that the version is written in bold type or that "Version" is not present in the thread.

Should switch back to get the version from the title?

Additional context
Some threads on which the problem occurred:

• https://f95zone.to/threads/the-winds-disciple-pixel-games.447/
• https://f95zone.to/threads/638

Description

Escaping non-special characters in strings, template literals, and regular expressions doesn't have any effect, as demonstrated in the following example: js let foo = "hol\a"; // > foo = "hola" let bar = `${foo}\!`; // > bar = "hola!" let baz = /\:/ // same functionality with /:/ Example …

Occurrences

There is 1 occurrence of this issue in the repository.

See all occurrences on DeepSource → deepsource.io/gh/MillenniumEarl/F95API/issue/JS-0097/occurrences/

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

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• Update actions/cache action to v3.3.3
• Update codecov/codecov-action action to v3.1.6
• Update dependency @types/node to v18.19.33
• Update dependency axios to v1.6.8
• Update dependency chai-as-promised to v7.1.2
• Update dependency tough-cookie to v4.1.4
• Update dependency chai to v4.4.1 (chai, @types/chai)
• Update dependency dotenv to v16.4.5
• Update dependency eslint to v8.57.0
• Update dependency js-sha256 to ^0.11.0
• Update dependency mocha to v10.4.0
• Update dependency typescript to v5.4.5
• Update typescript-eslint monorepo to v6.21.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Update actions/cache action to v4
• Update codecov/codecov-action action to v4
• Update dependency axios-cookiejar-support to v5
• Update dependency eslint to v9
• Update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• 🔐 Create all rate-limited PRs at once 🔐

Open

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

• Update dependency inquirer to v9.2.22
• Update actions/checkout action to v4
• Update actions/setup-node action to v4
• Update dependency @types/node to v20
• Update dependency axios-retry to v4
• Update dependency c8 to v9
• Update dependency chai to v5
• Update dependency eslint-plugin-prettier to v5
• Update dependency prettier to v3
• Update github/codeql-action action to v3
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

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

Hey mate! I'm going to use your npm package f95api for my project and instead of this I think it will be a good idea to ask you join us with developing our project which is similar to yours. We've got 1 junior frontend, 1 junior+ frontend< 1 ux/ui designer and me node.js senior dev/PM/team lead. If you interested - welcome to my telegram @fpavlik or email [email protected]
Hope to see you soon :3

Describe the bug
When I npm run the example I get the error show in the screenshot

To Reproduce
Steps to reproduce the behavior:

1. Go to 'termina'
2. Run on 'npm run example'
3. See error

Expected behavior
For the example to work.

Screenshots

Desktop (please complete the following information):

• OS: Windows 11
• Browser: Brave
• Version: 1.51.114