deploy_feedback VS TypeScript

Hey all, Andy from the Deno team here. We're excited to share with you Deno Subhosting, an easy way to extend your platforms functionality by securely running untrusted JavaScript written by your users.

When we first launched [Deno Deploy](https://deno.com/deploy) in 2021, we were surprised at the volume of requests from companies about getting access to the APIs needed to run Deno Deploy. Many companies wanted to give their users the ability to write custom logic in their app, but setting this up in the cloud presents security concerns and a ton of infra work/maintenance.

We realized that there was an opportunity for Subhosting to solve a larger problem, which is allowing companies to easily and securely run custom code written by their users, without the hassle of maintaining said infrastructure.

Though we do have a few subhosting customers (Netlify being one of them), this launch makes our Subhosting product self-service, so any development team interested in extending their platform via their users' custom code can do so by [signing up](http://dash.deno.com/subhosting/new_auto) and [reading our docs](https://docs.deno.com/deploy/manual/subhosting). We have [an updated pricing model for Subhosting](https://deno.com/deploy/pricing?subhosting) as well, including a generous free tier fit for kicking the tires and building a proof-of-concept.

We'd love to get your feed back. Have you ever talked to your co-workers about allowing external devs to "have at it" with your platform? What would it look like to unlock the final 10% for your top customers? How have you approached this problem in the past?

Thanks for reading and the Deno team will be responding to comments!

[Read the announcement blog post.](https://deno.com/blog/subhosting)

That means we don’t need to transpile the Typescript code to ESM or CJS. Currently, only Deno Deploy can run your Typescript function out of the box. However, in order to keep the code small, we still need some sort of bundling. Luckily, Bun is also a bundler 😉

What type of apps do you code for your day-job? (I program for fun and curiosity, so that is why I ask that lame question.)

Do you use node.js? Deno is brought in part by the Node.js creator, Ryan Dahl, who wanted to fix/improve a lot of things he didn't like in node.js.

They also have "Deno Deploy" (with a free tier) to run your code on different servers scattered throughout the globe: https://deno.com/deploy

One of the reasons I love the `deno` executable is you can use `import` statements in your code and then tell `deno` to merge everything into a single .js file. I would then take that and publish it to Cloudflare Workers. I know you can do this with node.js and a bunch of tools, but it is so much simpler with `deno`.

The online version of DocTrack is hosted through Deno Deploy and is accessible here.

It runs on https://deno.com/deploy which runs on gcp at the moment but my understanding is that the underlying cloud provider could change at any time.

For deployment Deno offers it's own service, Deno Deploy:

https://deno.com/deploy

Disclaimer: Haven't used it yet.

Deno functions. Its different than docker containers that auto scale. https://deno.com/deploy

One of the biggest annoyances with Deno deploy/functions is that there is no way to store any data. This would be very useful to e.g. cache an auth token, store a key/value pair, etc. See also: https://github.com/denoland/deploy_feedback/issues/110

Is any work being done to fix this? Or is this out of scope currently?

One of the valuable features of Solid Start is that you can use so-called "adapters" to completely change the output into something deployable basically everywhere that serves pages and with quite a lot of options: there are adapters for amazon web services, cloudflare pages and workers, deno deploy, netlify, standard node server (the default), vercel, and static deployment - the latter allows us to build something that we can put on github pages.

Regular expressions are part of the language, so it's not so unreasonable that TypeScript should parse them and take their semantics into account. Indeed, TypeScript 5.5 will include [new support for syntax checking of regular expressions](https://github.com/microsoft/TypeScript/pull/55600), and presumably they'll eventually be able to solve the problem the GP highlighted on top of those foundations.

Dedicated syntax for creating unique subsets of a type that denote a particular refinement is a longstanding ask[2] - and very useful, we've experimented with implementations.[3]

I don't think it has any relation to runtime type checking at all. It's refinement types, [4] or newtypes[5] depending on the details and how you shape it.

[1] https://github.com/microsoft/TypeScript/blob/main/src/compil...

GitHub | Website

Learning Curve and Developer Tooling sCrypt is an embedded Domain Specific Language (eDSL) based on TypeScript. It is strictly a subset of TypeScript, so all sCrypt code is valid TypeScript. TypeScript is chosen as the host language because it provides an easy, familiar language (JavaScript), but with type safety. There’s an abundance of learning materials available for TypeScript and thus sCrypt, including online tutorials, courses, documentation, and community support. This makes it relatively easy for beginners to start learning. It also has a vast ecosystem with numerous libraries and frameworks (e.g., React, Angular, Vue) that can simplify development and integration with Web2 applications.

As a JavaScript or TypeScript developer, you might have come across the terms type and interface when working with complex data structures or defining custom types. While both serve similar purposes, they have distinct characteristics that influence when to use them. In this blog post, we'll delve into the differences between types and interfaces in TypeScript, providing examples to aid your understanding.

TypeScript helps you in many ways in the context of a JavaScript app. It makes it easier to consume interfaces of any type.

In this guide, we'll be extracting information from Amazon product pages using the power of TypeScript in combination with the Cheerio and Crawlee libraries. We'll explore how to retrieve and extract detailed product data such as titles, prices, image URLs, and more from Amazon's vast marketplace. We'll also discuss handling potential blocking issues that may arise during the scraping process.

TypeScript

Familiarity with TypeScript, React and Next.js