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
A lot of NPM packages rely on the URL.protocol method to dictate various functionalities related to network connections i.e. for instance, the SurrealDB JS library
Solution
Adding support for URL would allow for advanced functionalities within packages like SurrealDB JS, among others.
Additional Context
N/A
The text was updated successfully, but these errors were encountered:
Hi, URL is not part of the JS spec, it a web API provided by the integrator of the JSVM (the web browser, NodeJS, etc). We periodically get requests like this and do appreciate that it would be convenient to provide APIs like this "out of the box". However it is not practical for our team to maintain an ever expanding set of Web APIs, which are not in our area of expertise.
I have previously suggested that it might make sense to create a separate project with a repository of common non-EcmaScript APIs.
Problem
A lot of NPM packages rely on the
URL.protocol
method to dictate various functionalities related to network connections i.e. for instance, the SurrealDB JS librarySolution
Adding support for
URL
would allow for advanced functionalities within packages like SurrealDB JS, among others.Additional Context
N/A
The text was updated successfully, but these errors were encountered: