nodejs.dev VS wasm-pack

[ { "type_of": "article", "id": 1281931, "title": "When can you declare yourself a Full-stack Dev?", "description": "Hello 👋🏼 I was wondering if I should consider myself as a front-end or full-stack developer. Or at...", "published": true, "published_at": "2022-12-02T17:05:00.000Z", "slug": "when-can-you-declare-yourself-a-full-stack-dev-31j1", "path": "/thomasbnt/when-can-you-declare-yourself-a-full-stack-dev-31j1", "url": "https://dev.to/thomasbnt/when-can-you-declare-yourself-a-full-stack-dev-31j1", "comments_count": 29, "public_reactions_count": 34, "page_views_count": ----, "published_timestamp": "2022-12-02T17:05:00Z", "body_markdown": "Hello 👋🏼\n\nI was wondering if I should consider myself as a front-end or full-stack developer. Or at least how to present myself to companies.\n\nAnd then, I asked myself... **at what moment can you consider yourself a full-stack developer?** What are the basics to know to become one? \n\n\n> For example, \n> I suppose that to be a self-proclaimed full-stack developer in JavaScript, you have to know at least one front-end framework (like [`Vue`](https://vuejs.org), [`React`](https://reactjs.org/), [`Angular`](https://angular.io/), [`Svelte`](https://svelte.dev/), [`Astro`](https://astro.build/) etc...), know the basics of the backend and its specificities, especially [`Node.js`](https://nodejs.dev) and all its aspects, know one or more frameworks (I think of [`Express.js`](https://expressjs.com/) or [`Fastify`](https://www.fastify.io/)), know how to create an API and databases, and know the principle of MVC in order to set up a good architecture. \n> \n> _If there is something missing, don't hesitate to tell me_.", "positive_reactions_count": 34, "cover_image": "https://res.cloudinary.com/practicaldev/image/fetch/s--CzOg3CT7--/c_imagga_scale,f_auto,fl_progressive,h_420,q_auto,w_1000/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/15u06okn5tcdc0i92xhm.png", "tag_list": [ "discuss" ], "canonical_url": "https://dev.to/thomasbnt/when-can-you-declare-yourself-a-full-stack-dev-31j1", "reading_time_minutes": 1, "user": { "name": "Thomas Bnt", "username": "thomasbnt", "twitter_username": "Thomasbnt_", "github_username": "thomasbnt", "user_id": 18254, "website_url": "https://thomasbnt.dev", "profile_image": "https://res.cloudinary.com/practicaldev/image/fetch/s--zpCwDOpw--/c_fill,f_auto,fl_progressive,h_640,q_auto,w_640/https://dev-to-uploads.s3.amazonaws.com/uploads/user/profile_image/18254/c3e35d32-bfe2-48ed-93b7-f2caf9c60gd7.png", "profile_image_90": "https://res.cloudinary.com/practicaldev/image/fetch/s--Iv24f4-g--/c_fill,f_auto,fl_progressive,h_90,q_auto,w_90/https://dev-to-uploads.s3.amazonaws.com/uploads/user/profile_image/18254/c3e35d32-bfe2-48ed-93b7-f2caf9c60gd7.pngg" }, "flare_tag": { "name": "discuss", "bg_color_hex": "#1ad643", "text_color_hex": "#FFFFFF" } }, ]

For example, I suppose that to be a self-proclaimed full-stack developer in JavaScript, you have to know at least one front-end framework (like Vue, React, Angular, Svelte, Astro etc...), know the basics of the backend and its specificities, especially Node.js and all its aspects, know one or more frameworks (I think of Express.js or Fastify), know how to create an API and databases, and know the principle of MVC in order to set up a good architecture.

nodejs.dev: Nodejs.org website Added a simple GitHub action to sync auto-generated docs daily, and added prettier formatting for .yml files

the Tutorial at nodejs.dev explains how node works and how it's different from other JS environments. They also have a version of the API docs which I find has better formatting than the one at nodejs.com

https://nodejs.dev/

I think this has been fixed here https://github.com/nodejs/nodejs.dev/pull/2713/files

Probably just pending release

I believe https://nodejs.dev/ is a third party site not officially related to the Node.js project.

Strapi is the leading open-source headless Content Management System (CMS). It is 100% Javascript, based on Node.js, and used to build RESTful APIs and GraphQL.

NestJS is a Node.js framework for building server-side applications. NestJS supports typescript out of the box. On the other hand, Passport is an authentication middleware for Node.js that supports over 500 authentication strategies, e.g., username and password, google, Facebook, etc.

For a much simpler but less flexible approach there's wasm-pack for creating JS packages from Rust, and wasm-bindgen for easy interop. Both have very good documentation.

After four years, I found some time to pay that deb-tech (yes, quite a long time, eh). To make it fun I rewrote everything from scratch in SolidJS, which went smooth thanks to this amazing library p5js-wrapper. For WASM, C++ is still a good choice, but what about Rust? I did some research and found wasm-pack. A few lines in the cargo.toml file and we were ready to generate compiled + ready to import bytecode!

Support using wasm-pack in Worklets (particularly AudioWorklet) #689

If you're looking to use it to interface with node/browsers, then try wasm-pack.

Webassembly: wasm-bindgen 0.2.83 / wasm-pack 0.10.3

wasm-pack has bugs - it publishes a module which declares itself as a commonjs module. (You can fix that by manually adding "type": "module" in package.json). Then the web build should work with other bundlers. I opened an issue about this over a year ago. There's a PR and everything, but no movement :/

wasm-pack helps you build Rust-generated WebAssembly packages and use it in the browser or with Node.js.

Is the Rust WASM ecosystem being half dead better? wasm-pack and wasm-bindgen are barely maintained anymore, and trust me it's not because everything works flawlessly…

I've been learning Rust for the past few weeks and have been enjoying it a lot.

- The community is very helpful on Discord (https://discord.com/invite/rust-lang-community).

- The package ecosystem (crates.io) makes it very easy to find and import things, and they're consistently documented.

- There's a path to compiling on web via WebAssembly (https://rustwasm.github.io/wasm-pack/)

In a few weeks of learning the language, I managed to put together this visualization: https://twitter.com/admiralakk/status/1542560489091350529

But realistically, either Go or Rust will be fine. You should pick the one you're more likely to stick with and learn, even when it gets tough. I've found the community aspect to be very helpful, because then at least I know I'm not the only idiot out there.

There are various ways to set up a web project that uses Svelte, Wasm, and Rust. For example, wasm-pack from the rust-wasm group provides a template for simple HTML-CSS-JS applications. There are also several project templates for React or Svelte with Rust and Wasm.