Dockery/Trilium
1
0
Fork 0
mirror of https://github.com/zadam/trilium.git synced 2025-11-03 11:56:01 +01:00
Code Issues Packages Projects Releases Activity

use .js extension for require() as a preparation for future migration to ESM

Browse Source
This commit is contained in:
zadam
2023-11-22 19:34:48 +01:00
parent 722299dd26
commit cf99345962
189 changed files with 984 additions and 984 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
src/routes/api/script.js
View File

@@ -1,10 +1,10 @@
"use strict";
const scriptService = require('../../services/script');
const attributeService = require('../../services/attributes');
const becca = require('../../becca/becca');
const syncService = require('../../services/sync');
const sql = require('../../services/sql');
const scriptService = require('../../services/script.js');
const attributeService = require('../../services/attributes.js');
const becca = require('../../becca/becca.js');
const syncService = require('../../services/sync.js');
const sql = require('../../services/sql.js');
// The async/await here is very confusing, because the body.script may, but may not be async. If it is async, then we
// need to await it and make the complete response including metadata available in a Promise, so that the route detects