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
There was general consensus about the approach, there was some questions raised about the workflow. @bartlomieju indicated that we have proven all the workflow in one way or another.
ACTION proceed with breaking out the manual to a seperate repo.
Robust conversation about if this a good thing or bad thing. Strong arguments that any "bypass" will lead people to weaken their security, often unintentionally. Strong arguments though that legitimate development often leads to situations where the CLI would need to connect to an "invalid" secure connection.
Strong agreement that it should make it very clear that you are doing something "bad" like Chrome's --unsafely-treat-insecure-origin-as-secure flag and make it very explicit and narrow.
ACTION we need to improve documentation about current ways of dealing with self-signed or unrecognised trust authorities that come up when developing.
ACTION Proceed with introducing a flag to bypass "invalid" certificates. (Noted, that there was not unanimous consensus on this action)
Mostly the infrastructure is ready (core, cli, swc).
TypeScript (tsc) still doesn't have support. The changes will not make TypeScript 4.4 so the earliest is TypeScript 4.5 (late-October). Discussed that if it was just a "diagnostic" issue, but didn't mess up the emit, that we might be able to move forward, but identified that the TypeScript emit borks the code.
No choice but to move it to Q4. 😢
How do we deal with the design of the standard library?
The public forums around std stopped earlier this year because they weren't as effective as needed.
Lots of discussion about how much of the core teams discussions should be made public. General consensus was that we should continue issuing the minutes like this for now.
General agreement that we don't want more meetings if we can avoid it.
ACTION the std library and it design discussion will be part of the CLI Roadmap and the CLI Design Meetings. We will re-evaluate if it doesn't work effectively.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
deno
executable (sign binaries #575)deno compile
signing is going to be complex and not in scope for this.--unsafely-treat-insecure-origin-as-secure
flag and make it very explicit and narrow.tsc
) still doesn't have support. The changes will not make TypeScript 4.4 so the earliest is TypeScript 4.5 (late-October). Discussed that if it was just a "diagnostic" issue, but didn't mess up the emit, that we might be able to move forward, but identified that the TypeScript emit borks the code.std
stopped earlier this year because they weren't as effective as needed.std
library and it design discussion will be part of the CLI Roadmap and the CLI Design Meetings. We will re-evaluate if it doesn't work effectively.h
andFragment
for JSX #11186 it might make sense to standardise on the new JSX transforms than other varieties.Beta Was this translation helpful? Give feedback.
All reactions