Can't seem to find an official docs link for allow-net, only blog posts.
https://github.com/nodejs/node/pull/58517 - I think the `semver-major` and the timing mean that it might not be available until v25, around October
Readit Newstchetwin commented on Modern Node.js Patterns kashw1n.com/blog/nodejs-2... · Posted by u/eustoria
tchetwin commented on ts-blank-space is a fast type-stripping compiler bloomberg.github.io/ts-bl... · Posted by u/joatmon-snoo
Doesn't the new node feature to strip types handle this already? https://nodejs.org/en/learn/typescript/run-natively
I haven't used it as I haven't had a need for it.
It does!
Node uses swc to do this. The swc implementation of blank-spacing (implemented here https://github.com/swc-project/swc/pull/9144) was inspired by the author of ts-blank-space here: https://gist.github.com/acutmore/27444a9dbfa515a10b25f0d4707.... It has just taken a little longer to release the original implementation.
Very tempted! Installation instructions?
`npx` is a tool that ships alongside `npm` (alongside `node`) that either finds a local installation or performs a just-in-time download, and then runs the default "bin" entrypoint for the package.
Newer versions of `npx` (last few years) will prompt the user before installing a package. Older versions did not. Note that installing the package can run arbitrary scripts as a side effect with at least the level of permission of the current user, so there is implicit trust required of the author, and the authors of all transitive dependencies.
https://www.apple.com/support/systemstatus/
Weather - Issue
Today, 4:00 AM - ongoing
Some users are affected
Next-hour precipitation may be unavailable for Alaska due to a data provider outage.tchetwin commented on Insights from Adopting TypeScript at Scale techatbloomberg.com/blog/... · Posted by u/robpalmer
> undesirable features by preventing their use.
I wonder if they have published those rules, I'd like to see them as I'm just diving into TS.
These rules are currently a not-readily-separable part of our build tooling. To provide earlier feedback for developers we're intending to standardise on an ESLint ruleset that will probably comprise the `no-restricted-syntax` rule: https://eslint.org/docs/rules/no-restricted-syntax