Right now all the html files share some common values in the tag; it would be better to use vue-head in order to create a single file component with those values.

Some values are page-specific (e.g. page tile, favicon), those should be configured as props so that every page can customize it.
Some pages have specific JS code, that can be left out of the Vue component.

Issue generated from L4W bug reporting interface
User #6 wrote:

tst

The project uses Vue.js 2, I would like to upgrade it to version 3.1.0 (or later).
Vue components are here: /src/client/components/
Vue 3 breaking changes can be found here: https://v3.vuejs.org/guide/migration/introduction.html#breaking-changes
Migration build could be useful: https://github.com/vuejs/vue-next/tree/master/packages/vue-compat

Problem statement & steps to replicate

When using WASD to move on the map, if you press one key and keep it pressed, the hero will:

1. Do one step
2. Pause
3. Move again, this time without pausing

Expected behaviour

A movement without any pause as long as the same key is pressed down.

Preliminary analysis

This happens because only for the first movement, the "keydown" event (see method "init" of Input.ts) always arrives after the step is completed (see method "manageMovements" of EventManager.ts).
Making the check in "manageMovements" async with a setTimeout(fn, 0) did not help.
No idea how to fix this...

TSLint has been deprecated in favor of ESLint: palantir/tslint#4534
Should remove TSLint from the Grunt script and replace it with ESLint, maitaining the rules defined in the TSLint configuration file

Issue generated by L4W bug reporting interface
User #26 wrote:

Test fdfg
dfgdfgsd
dfgdsfg

\n
/n

asdasd

#asdasd
?> alert()
" ' } {}{* eval(

https://developers.facebook.com/docs/graph-api/changelog

Issue generated from L4W bug reporting interface
User #26 wrote:

test

teasfsdf

sdfdf

sdfsdf

Issue generated from L4W bug reporting interface
User #26 wrote:

(###)
<a hr#f="">

\n
\r
}[#v#,;c sd

Issue generated from L4W bug reporting interface
User #26 wrote:

Test

test

The legacy Google Sign-In web solution will no longer be supported after March 31, 2023.

Migration to the new Google Identity Services - new family of Identity APIs that consolidate multiple identity offerings under one software development kit (SDK) - will be necessary to sign in users using their Google Account to your platform, after that date. The SDK will use the new Sign In With Google client library.

Migrate to the new Google Identity Services by following the migration guide: https://developers.google.com/identity/gsi/web/guides/migration

I would like to add a logo to this project.
It should contain the name "L4W", and have a pixel-art/fantasy vibe.
Preferred format is around 200x100px with transparent background (PNG or GIF), or vectorial image.
You can add the image in this path: /style/logo/
I will accept any PR for this as long as the proposed logo shows some effort (no spam please)

The BugReporting component (visible in the home page) includes reCAPTCHA v3: /src/client/components/BugReporting.vue#L3-L4

It would be better to add the script tag only if its is needed, in order to reduce load times and avoid having the reCAPTCHA overlay shown in the page when it is not really used:

The script tag should be added to the page when the user types something in the text-area: /src/client/components/BugReporting.vue#L1

Upgrade lowdb to version 3.0.0, and migrate existing code: https://github.com/giovannipessiva/l4w/blob/master/src/server/database.ts

Issue generated by L4W bug reporting interface
User #26 wrote:

test

Issue generated by L4W bug reporting interface
User #26 wrote:

test

Issue generated by L4W bug reporting interface
User #26 wrote:

asd
asd

<script>alert(1)</script>

\n
\r
}[#v#,;c sd