Last 12 weeks · 0 commits
4 of 6 standards met
When I am serving a specific directory the devtools always complain that the source maps couldn't be loaded. That also makes sense cause Chrome will try to fetch those relative to directory that is served, meaning it looks for source maps in and obviously it cannot find them there, cause that path is not a correct path to the node modules where the source maps are located. Any idea what I could do to fix this?
Description When registering multiple custom schemes using , (and other Web Crypto API methods) throw errors in windows using schemes that weren't registered last. Expected Behavior All registered schemes should have proper secure context privileges, allowing to work regardless of registration order. Root Cause According to Electron's documentation, should be called once before the app's ready event, with all schemes registered together. Multiple calls may interfere with each other, causing only the last registration to properly establish secure context. Looking at the source code, each call to calls separately: Reproduction Proposed Solution could collect all scheme registrations via a "batch method" and call once with all schemes before .
Repository: sindresorhus/electron-serve. Description: Static file serving for Electron apps Stars: 482, Forks: 35. Primary language: JavaScript. Languages: JavaScript (92%), HTML (8%). License: MIT. Topics: electron, electron-module, nodejs, npm-package, serve, server, single-page-app, static-file-server. Latest release: v3.0.1 (5mo ago). Open PRs: 0, open issues: 0. Last activity: 5mo ago. Community health: 71%. Top contributors: sindresorhus, hadeeb, dedo1911, mhkeller, akshitkrnagpal, ffflorian, ibash, itsonlyjames, juliangruber, lazToum and others.