Files
feuerwerk/src/core/store/projectPlugins.ts
T
adminandClaude Opus 5 5ba796a2b6
game-maker / gate (push) Successful in 3m32s
game-maker / suite (push) Failing after 8m21s
Plugins belong to the project, and they load before it: the project file gained the field plugins: ["demo-plugin.js"] (default empty, no formatVersion bump), the Plugins tab's switch writes into it as an ordinary undo step (SetPluginActiveCommand) instead of into a server-wide plugins.json, and the start order is turned around - startPlugins only fetches the list of files, then editor.boot() runs and ProjectStore.load(id, prepare) hands the raw JSON through before it is deserialized, where pluginsOf(raw) reads the list and PluginManager.syncTo() activates exactly those; that is the point of the issue, because what a plugin registers has to stand there before normalizeGraph would throw it away as unknown (#126, #127), a project switch first stops what the new project does not name and then starts what it does, a file the server does not have is passed over silently, and after signing out the manager is dead so a late event cannot start anything in a torn-down session; on the server plugins.json, PluginStore::setActive, isActive, the route PUT ?r=plugins/{file} and the 403 for inactive modules are gone and GET ?r=plugins only answers {file,bytes,updatedAt}, which makes every plugin file fetchable - the consequence accepted in #117, written down in the wiki for #115 and #116; publishPlugins(root) only copies files now, the seeder switches the demo plugin on in the fixture project, and the Plugins tab carries a puzzle piece as its icon while only a plugin's own tab still goes without one (the knob and the socket are cubic curves, not arcs, which Pixi's parser draws as a spike after an L); 3 new e2e checks in module 38 and 5 new unit tests cover the project as the owner of the switch, its undo, the order, pluginsOf against crude input and an unknown file name (#119)
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-20 14:24:27 +02:00

16 lines
859 B
TypeScript

/**
* Which plugins a project switches on (#119), read straight off the untrusted JSON of the project
* file. This is deliberately its own module rather than a part of `deserializeProject`: the editor
* has to know the list *before* it deserializes anything, because a plugin may add node types and
* asset kinds that the deserializer would otherwise throw away as unknown.
*/
export function pluginsOf(raw: unknown): string[] {
const list = (raw as { plugins?: unknown } | null)?.plugins;
const files = (Array.isArray(list) ? list : []).filter(
(file): file is string => typeof file === 'string' && file !== '',
);
// Sorted and without repeats: that is also the order the loader activates them in, so a project
// file written by hand cannot make one plugin come before another by listing it first.
return [...new Set(files)].sort();
}