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
{{ message }}
This repository was archived by the owner on Jan 25, 2022. It is now read-only.
@meteorplus This repo is a proposal for a feature that is still being standardized. Issues on this repo are meant for problems with the proposal. Browser implementation issues should be be taken up in the respective browser issue tracker. MDN has more information on the implementation status.
If you believe there is an issue with the proposal, providing more information about what you are expecting will probably help the people managing this proposal know how to respond.
my proposal is to have an allowed path or file which the dynamic import function checks before loading those files something like:
//config allowed imports on the server:
import.config(['path/to/something.js','path/to/a/folder']); //this might be a file path or folder path
//then on the client
const path = "/server/mysuperprivatesecret.js", path2 = "path/to/something.js";
import(path);// this will fail since it's not allowed
import(path2);//will not failt because it is allowed
What do you think?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello all,
It is very sad this is still an issue at 2018, I meant I thought this is something normal and expected with dynamic import!!
JQuery had this in 2008 like a decade ago you could import anything in the browser with no issues at all!!
What is this? are going steps back??
The text was updated successfully, but these errors were encountered: