Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking of Incompatible Plugins #1101

Open
balupton opened this issue Aug 6, 2020 · 0 comments
Open

Tracking of Incompatible Plugins #1101

balupton opened this issue Aug 6, 2020 · 0 comments

Comments

@balupton
Copy link
Member

balupton commented Aug 6, 2020

I've updated all the plugins this week using boundation to make them compatible with the latest DocPad conventions (targeting v6.83.1 specifically, as v6.80.0 brought CoffeeScript v2 which broke several old plugins, and v6.82.0 encouraged the use of getPath).

The following plugins have had their conventions updated, however need a volunteer to fix their tests:

These can probably be marked as deprecated, with the solutions being things outside of docpad's ecosystem, such as cloudflare worker redirects:

The following plugins I am working on fixing their tests:

These ones were working, but now they aren't:

The following plugins I am unable to do anything about:

/cc @jlukic @docpad/extras-team


You can use npm test -- --debug to have docpad-plugintester configure DocPad to the debug log level.


Rewrites to JavaScript would be great:

  1. rename source files from .coffee to .js
  2. run boundation on it, selecting esnext as the only language (uncheck coffeescript), this will configure all the scripts and compilation and editor etc for javascript
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant