proposal-function-implementation-hiding
proposal-function-implementation-hiding copied to clipboard
tc39
JavaScript language proposal: function implementation hiding
Can we give application owners the ability to disable the directives from any library that uses them? If I own the application, I can always lint for libraries that have...
Hermes (and probably Moddable, QuickJS, etc?) doesn't preserve the source by default since everything is compiled to bytecode in advance. In other words "hide source" is the default. It seems...
Maybe I didn't notice it in the `README.md`, but I don't really understand how this will help to conceal sensitive code if you either get the packages via `npm i`,...
Hello. I've checked all issues but did not find one - please correct me if I'm wrong. I assume this is expected to be a common pragma in library apps:...
I'm curious to know if it would be better to have a syntax for this requirement; Maybe something like: ```javascript async function connectToDB(connStr) #{ return await orm.connect(connStr) } ``` (It...
This proposal mentions the following: > A historical example of this in action is AngularJS's reliance on f.toString() to inspect the parameter names of a function. It would then use...
I currently have specced `"use no Function.prototype.toString"`. This might be fine. It's pretty clear on what it does. Any other suggestions?
In V8, some error messages currently expose the source text of an ES-code function. ```js try { Uint8Array.from.call(x => x + 3); } catch (err) { err.message; } → 'x...
What does top-level directives do? ``` 'hide source'; function foo() { /* no hide source */ } // inherit? function bar() { 'show source' } // override? ``` Would it...
@michaelficarra hi, this is a clarifying question, not an issue. But this looks like the best place to put it. It is unclear to me how users will use both...
