رفع یک سری باگ و افزودن یک سری ویژگی از جمله:
Support longPolling transport raise reconnect in JS client and .Net client when network disconnect
Support reporting progress from hub method invocations
Add ability to provide an interface for client methods via Hub
و ...
Here’s a quick list of what’s new in TypeScript 4.7!
ECMAScript Module Support in Node.js
Control over Module Detection
Control-Flow Analysis for Bracketed Element Access
Improved Function Inference in Objects and Methods
Instantiation Expressions
extends Constraints on infer Type Variables
Optional Variance Annotations for Type Parameters
Resolution Customization with moduleSuffixes
resolution-mode
Go to Source Definition
Groups-Aware Organize Imports
Object Method Snippet Completions
Breaking Changes
Let’s take a look at what’s in store for TypeScript 4.2!
in Operator --noPropertyAccessFromIndexSignature abstract Construct Signatures --explainFiles Flag 
Irrespective of what technologies your remote team uses, there are numerous VS Code plugins you will find useful, but this article will only cover those I have used extensively.
Apparently, there are “true” and “false” operators and you can overload these. But I also wanted to know what are these good for, given I’ve never heard about these.
Preview 6 is the second to last preview before we enter the RC period. There will be two RCs. This release itself is relatively small, while Preview 7 will be bigger.
The .NET Micro Framework team is pleased to announce the release of .NET Micro Framework 4.4. We fixed several long outstanding issues as well as improved the reliability of lwIP network stack and debugging experience through Visual Studio 2015.
This release brings continued improvements to the C# and .NET experiences, new Git performance and experiences, updates for C++ developers, and new Azure tools for local development and deployment. We also continue to address your direct feedback submitted via Developer Community, addressing over 400 feedback items in this release! You can see the broader list of community feedback addressed in releases by visiting the fixes page on Developer Community.
version: '3'
networks:
shared-network:
services:
nodeapp1:
image: nodeapp1
build:
context: nodeapp1
dockerfile: dockerfile
ports:
- "8181:80"
networks:
- shared-network
nodeapp2:
image: nodeapp2
build:
context: nodeapp2
dockerfile: dockerfile
ports:
- "8182:80"
networks:
- shared-network
mongo:
image: mongo
ports:
- "27017:27017"
networks:
- shared-network docker-compose build
docker-compose up
docker-compose down
docker-compose stop
docker-compose start
docker-compose run --build
FROM node COPY . /var/www WORKDIR /var/www RUN npm i EXPOSE 80 ENTRYPOINT node index
const express = require('express');
const fetch = require('node-fetch');
const app = express();
app.get('/', async (req, res) => {
let response = await fetch("http://nodeapp2/");
text = await response.text();
res.send(text);
})
app.listen(80, () => console.log(`listening on port 80!`)) version: '3' services: nodeapp1: environment: - PRODUCTION: 'true' nodeapp2: environment: - PRODUCTION: 'true'
docker-compose -f docker-compose.yml -f docker-compose.prod.yml up