v2.1.3

Lapcord v2.1.3

Features

• Update volt.toml for @doupkg/lapcord
• Cache system for fetching versions
• New views for Mostache, for more keys and customization into config
• Implementing Mocha tests
• Fetch new version for update
• Better error handling
• Implement config logic
• Logging events into Lapce logs
• Implement OOP principles

Declined

• New languages to support: Please suggest which languages or services to add. I'm open to recommendations as I'm unsure about the specific languages or services to include.
• Output logs (Successful connection, errors, information, etc.): Lapce doesn't display output messages through connection.console. It only supports code lens functionality.
• Kick @Leoxyzua: he does nothing

v2.0.1

Lapcord v2.0.1

$ npm i -g lapcord
$ npm update -g lapcord

Bug fixes:

• Payload Activity Error (128+ length) #8
• Decode utf-8 uri for state and details

Features:

• Support to 120+ languages
• Better icons
• New idle presence

Soon

• Own config
• Button support
• Git repository button
• Number of code errors (maybe)

v1.2.2

Lapcord v1.2.2

Same as v1.2.0

Lapcord v1.2.0

We have fixed issue #8. We have also changed the code structure and replaced ESLint & Prettier with Rome. Several ESLint dependencies (all of them) were removed.

Features

• Rome formatter
• languages.json -> langs/

v1.2.0

Lapcord v1.2.0

We have fixed issue #8. We have also changed the code structure and replaced ESLint & Prettier with Rome. Several ESLint dependencies (all of them) were removed.

Features

• Rome formatter
• languages.json -> langs/

v1.0.2

Lapcord v1.0.2

Nothing new, we just changed the name of the organization.

Same code. Same bugs.

v1.0.1

Lapcord v1.0.1

If you download this package for use with the Lapcord extension, available for Lapce, test it as much as possible and report any bugs.

Features

• Nothing, lol

It is the first version, it works, obviously, but in a delimited way because it is impossible to create an IPC that connects to Discord using WASI, so we opted to use an LSP to register the events. But still, apparently, speaking from ignorance, the client that Lapce offers to connect to a LSP does not send events in the way we expected.

Install

yarn global add lapcord-server
npm install --global lapcord-server