You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
difficult as the underlying feedr library is deprecated, perhaps best to just make a new one called docpad-plugin-fetch or something, or just consider this one archived
The following plugins I am unable to do anything about:
docpad-plugin-copy - for bevry to update, it needs the maintainer to transfer to the docpad org and add bevryme as an npm owner, the docpad-plugin-raw could be used instead in the meantime
You can use npm test -- --debug to have docpad-plugintester configure DocPad to the debug log level.
Rewrites to JavaScript would be great:
rename source files from .coffee to .js
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
The text was updated successfully, but these errors were encountered:
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:
bevryme
as an npm owner, the docpad-plugin-raw could be used instead in the meantime/cc @jlukic @docpad/extras-team
You can use
npm test -- --debug
to havedocpad-plugintester
configure DocPad to the debug log level.Rewrites to JavaScript would be great:
esnext
as the only language (uncheckcoffeescript
), this will configure all the scripts and compilation and editor etc for javascriptThe text was updated successfully, but these errors were encountered: