Simply, the major version and minor version tagged in the [semver](https://semver.org/) string of [`@types/node`](https://www.npmjs.com/package/@types/node) is exactly corresponding to the node&#39;s version.

If you check the [`index.d.ts` file of `@types/node`](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/node/v8/index.d.ts) in [DefinitelyTyped](https://github.com/DefinitelyTyped/DefinitelyTyped) repository, you&#39;ll see what type of node is this declaration file for through the first line comment at the top of the file:

    // Type definitions for Node.js 8.10.x
    // Project: http://nodejs.org/
    ....




In react-router v3 we had activeStyle and activeClassName to style active Link

we could do something like this

      &lt;div id=&quot;tags-container&quot;&gt;
        {tags.map(t =&gt;
          &lt;Link
            className=&quot;tags&quot;
            activeStyle={{ color: &#39;red&#39; }}
            to={t.path}
          &gt;
            {t.title}
          &lt;/Link&gt;
        )}
      &lt;/div&gt;



I wanna know how can I do same thing in v4?

How can I style active Link in react-router v4?

I am new to GIT, so far I had been using Visual Studio Online TFS for my version control and I am the **only** developer. When I created my last project I was kind of mislead into thinking GIT was the best option for this.

So I checked-in my master. Then when I was going to work on a Feature I read I had to create a branch (this was not necessary in TFS) so I created &quot;development_print&quot; as a new branch and worked on my feature.

Now my feature is complete but I don&#39;t know how to merge it back into master. I am not interested in multiple branches at the moment, just want my new feature merged into master and remain with master.

In VS there is a **merge branch** option but it only allows me to merge into development_print (I want my feature into master!) so it does not let me set Into Current Branch and for Merge From Branch shows: 

 - Development_print
 - master
 - origin/development_print
 - origin/master

which is kind of confusing? it seems all backwards. So how do I get out of this mess without losing all the work I did on the feature?

Visual Studio 2015 How to merge a branch into master?

I&#39;m just started using node and wanted to try it with typescript. I did an `npm install @types/node` and the latest version was 7.0.4:


    $ npm install @types/node
    test-simple-node-typescript@0.1.0 /home/wink/prgs/test-simple-node-typescript
    └── @types/node@7.0.4 


Where as the latest version of node is 7.5.0:

    $ node --version
    v7.5.0

What is the relationship between the version of node.js and that of @types/node?

Relationship between the version of node.js and the version of @types/node

I'm just started using node and wanted to try it with typescript. I did an <code>npm install @types/node</code> and the latest version was 7.0.4:
<pre><code class="hljs language-ruby">$ npm install @types/node
test-simple-node-typescript@0.1.0 /home/wink/prgs/test-simple-node-typescript
└── @types/node@7.0.4 
</code></pre>
Where as the latest version of node is 7.5.0:
<pre><code class="hljs language-css">$ node --version
v7.5.0
</code></pre>
What is the relationship between the version of node.js and that of @types/node?

I am sorry for my very newbie question, but I am having a terrible day figuring out this error, I have an Express app and I am trying to run it in docker compose.
I&#39;ve used this Dockerfile:

    FROM mhart/alpine-node
    RUN mkdir -p /usr/src/app
    RUN chmod -R 777 /usr/src/app
    WORKDIR /usr/src/app
    RUN npm install node-gyp -g
    RUN npm install nodemon -g
    ENV NODE_ENV development
    EXPOSE 3000

And this portion of my docker-compose file:

    backend:
        mem_limit: 100m
        build:
          context: .
          dockerfile: dockerfiles/node/Dockerfile
        command: npm start
        depends_on:
          - mongo
          - elasticsearch
        volumes:
          - ./backend/:/usr/src/app
        ports:
          - 3000:3000
        links:
          - &quot;mongo:mongo&quot;
          - &quot;elasticsearch:elasticsearch&quot;

  When I do docker-compose up, I get this error:

    backend_1        | npm info it worked if it ends with ok
    backend_1        | npm info using npm@3.10.10
    backend_1        | npm info using node@v6.9.5
    backend_1        | npm info lifecycle service-designer@1.0.0~prestart: service-designer@1.0.0
    backend_1        | npm info lifecycle service-designer@1.0.0~start: service-designer@1.0.0
    backend_1        | 
    backend_1        | &gt; service-designer@1.0.0 start /usr/src/app
    backend_1        | &gt; nodemon index.js
    backend_1        | 
    backend_1        | [nodemon] 1.11.0
    backend_1        | [nodemon] to restart at any time, enter `rs`
    backend_1        | [nodemon] watching: *.*
    backend_1        | [nodemon] starting `node index.js`
    backend_1        | module.js:471
    backend_1        |     throw err;
    backend_1        |     ^
    backend_1        | 
    backend_1        | Error: Cannot find module &#39;dotenv&#39;
    backend_1        |     at Function.Module._resolveFilename (module.js:469:15)
    backend_1        |     at Function.Module._load (module.js:417:25)
    backend_1        |     at Module.require (module.js:497:17)
    backend_1        |     at require (internal/module.js:20:19)
    backend_1        |     at Object.&lt;anonymous&gt; (/usr/src/app/index.js:1:63)
    backend_1        |     at Module._compile (module.js:570:32)
    backend_1        |     at Object.Module._extensions..js (module.js:579:10)
    backend_1        |     at Module.load (module.js:487:32)
    backend_1        |     at tryModuleLoad (module.js:446:12)
    backend_1        |     at Function.Module._load (module.js:438:3)
    backend_1        | [nodemon] app crashed - waiting for file changes before starting...

If I do `ls -al` in the ***backend*** container, I get a full list of my backend app folder content, but it sounds like node_modules dependencies are not recognized.

 

Cannot find module for a node js app running in a docker compose environment

**SITUATION:**

I follow this tutorial: https://cloud.google.com/nodejs/tutorials/bookshelf-on-compute-engine

Everything works fine until I do `npm start` and go to:

http://localhost:8080

I am met with the following text on the blank page:

    Could not load the default credentials. Browse to https://developers.google.com/accounts/docs/application-default-credentials for more information.

Which makes no sense since I am using OAuth. I followed the link and read the page, but I have no `GOOGLE-APPLICATION-CREDENTIALS` field anywhere, and nothing about it in the tutorial.

-------

**QUESTION:**

Could you please reproduce the steps and tell me if you get the same result ?

(takes 5 minutes)

If not, what could I have done wrong ?

Could not load the default credentials? (Node.js Google Compute Engine tutorial)

I am trying to send the request from one localhost port to the another. I am using **angularjs on the frontend and node on the backend**.

Since it is **CORS** request, In node.js, i am using 

    res.header(&#39;Access-Control-Allow-Origin&#39;, &#39;*&#39;);
    res.header(&#39;Access-Control-Allow-Methods&#39;, &#39;GET, POST, PUT, DELETE, PATCH&#39;);
    res.header(&#39;Access-Control-Allow-Headers&#39;, &#39;Origin, X-Requested-With, Content-Type, Accept, Authorization&#39;);

and in the angular.js service file, I am using

    return {
        getValues: $resource(endpoint + &#39;/admin/getvalues&#39;, null, {
            &#39;get&#39;: {
                 method: &#39;GET&#39;,
                 headers:{&#39;Authorization&#39;:&#39;Bearer&#39;+&#39; &#39;+ $localStorage.token}
                 }
         }),
    }

I am getting the following error

**Request header field Authorization is not allowed by Access-Control-Allow-Headers in preflight response.**


Please help!



   

CORS error :Request header field Authorization is not allowed by Access-Control-Allow-Headers in preflight response

I have a node project written in typescript@2.

My tsconfig has `sourceMap` set to `true` and the `*.map.js` files are generated. When I execute my transpiled `*.js` JavaScript files via `node` or `nodemon`, I only see the error messages relative to the `js` file and not to the mapped typescript files; I assume it&#39;s completely ignored.

Is `sourceMap` support only intended for browser-support? Or can I use it together with node or nodemon? If the latter, how would I enable it?

I want to see runtime errors detected from an executed javascript file relative to the original typescript file.

Is there source map support for typescript in node / nodemon?

The following snippet shows a typescript error at **LINE 4**:

    import {Message} from &#39;./class/message&#39;;

    function sendPayload(payload : Object) : any{
       let message = new Message(payload);
       console.log(message);   // LINE 4 
    }

The error says:

    [ts] Cannot find name &#39;console&#39;.

What could be the reason for this? Why it cannot find the object `console`?


Cannot find name &#39;console&#39;. What could be the reason for this?

Recently, I have started  playing with angular 2. It&#39;s awesome so far. So, i have started a demo personal project for the sake of learning using `angular-cli`. 

With the basic routing setup, I now want to navigate to some routes from header, but since my header is a parent to the `router-outlet`, I receive this error. 

**app.component.html**
```html
&lt;app-header&gt;&lt;/app-header&gt; // Trying to navigate from this component
    &lt;router-outlet&gt;&lt;/router-outlet&gt;
&lt;app-footer&gt;&lt;/app-footer&gt;
```
**header.component.html**
```html
&lt;a [routerLink]=&quot;[&#39;/signin&#39;]&quot;&gt;Sign in&lt;/a&gt;
```
Now I understand partially I guess that since that component is a wrapper around `router-outlet` it would not be possible this way to access `router`. So, is there a possibility to access navigation from outside for a scenario like this?


I would be really happy to add any more information if needed. Thank you in advance. 

**Update**

1- My `package.json` already has the stable `@angular/router 3.3.1` version.
2- In my main `app` module, I have imported the `routing-module`. Please see below.

**app.module.ts**

    import { BrowserModule } from &#39;@angular/platform-browser&#39;;
    import { NgModule } from &#39;@angular/core&#39;;
    import { FormsModule } from &#39;@angular/forms&#39;;
    import { HttpModule } from &#39;@angular/http&#39;;
    import { AlertModule  } from &#39;ng2-bootstrap&#39;;
    import { LayoutModule } from &#39;./layout/layout.module&#39;;
    import { UsersModule } from &#39;./users/users.module&#39;;
    import { AppRoutingModule } from  &#39;./app-routing.module&#39;;
    import { AppComponent } from &#39;./app.component&#39;;
    import { PageNotFoundComponent } from &#39;./shared/components/not-found.component&#39;;
    
    @NgModule({
      declarations: [
        AppComponent,
        PageNotFoundComponent
      ],
      imports: [
        BrowserModule,
        FormsModule,
        HttpModule,
        AlertModule.forRoot(),
        LayoutModule,
        UsersModule,
        AppRoutingModule  --&gt; This is the routing module. 
      ],
      providers: [],
      bootstrap: [AppComponent]
    })
    export class AppModule { }

**app-routing.module.ts**

    import { NgModule } from &#39;@angular/core&#39;;
    import { Routes, RouterModule } from &#39;@angular/router&#39;;
    import { SigninComponent } from &#39;./users/signin/signin.component&#39;;
    import { PageNotFoundComponent } from &#39;./shared/components/not-found.component&#39;;
    
    const routes: Routes = [
    { path: &#39;**&#39;, component: PageNotFoundComponent }
    ];
    
    @NgModule({
        imports: [RouterModule.forRoot(routes)],
        exports: [RouterModule]
    })
    
    export class AppRoutingModule {}


The route I am trying to access is delegated from another `module` that is the `UsersModule`

**user-routing.module.ts**

    import { NgModule } from &#39;@angular/core&#39;;
    import { RouterModule, Routes } from &#39;@angular/router&#39;;
    import { SigninComponent } from &#39;./signin/signin.component&#39;;
    
    const usersRoutes: Routes = [
      { path: &#39;signin&#39;,  component: SigninComponent }
    ];
    @NgModule({
      imports: [
        RouterModule.forChild(usersRoutes)
      ],
      exports: [
        RouterModule
      ]
    })
    
    export class UsersRoutingModule { }

While I am trying to navigate from a component that is part of the `Layout` module, but has no notion of the router module. Is that what is causing the error. 

**Layout.module.ts**

    import { NgModule } from &#39;@angular/core&#39;;
    import { HeaderComponent } from &#39;./header/header.component&#39;;
    import { FooterComponent } from &#39;./footer/footer.component&#39;;
    
    @NgModule({
      declarations: [HeaderComponent, FooterComponent],
      exports: [HeaderComponent, FooterComponent]
    })
    export class LayoutModule{}

I am trying to navigate from the `HeaderComponent`. I would be happy to provide more information if needed.

Can&#39;t bind to &#39;routerLink&#39; since it isn&#39;t a known property

**I know it&#39;s kind of a bad practice**, but bear with me:

I&#39;m using Angular-CLI, particularly `ng g` to generate all of my classes. However, I&#39;m not interested in any `*.spec.ts` test files. I know that there are two flags (`--inline-template`, ` --inline-style`) to handle inline CSS and HTML instead of separated files, and for spec the `--spec` flag is set to true by default.

So for each run, yes, I could do `ng g c foo --it --is --spec=false`.

But how do I disable the creation of test files globally? Is there any default setting for it?

Rashly, I did some stuff **(that didn&#39;t work)**, like:

    ng set spec=false --global

I also tried configuring my `src/tsconfig.json` by filling the exclude array:

    &quot;exclude&quot;: [
        &quot;**/*.spec.ts&quot;
    ]

 

Angular 9 + CLI (TypeScript) - How to stop generating .spec.ts test files

I have this simple helloworld react app created from an online course, however I get this error:


&gt; Invalid configuration object. Webpack has been initialised using a
&gt; configuration object that does not match the API schema.
&gt;  - configuration has an unknown property &#39;postcss&#39;. These properties are valid:    object { amd?, bail?, cache?, context?, dependencies?,
&gt; devServer?, devtool?, entry, externals?, loader?, module?, name?,
&gt; node?, output?, performance?, plugins?, profile?, recordsInputPath?,
&gt; recordsO utputPath?, recordsPath?, resolve?, resolveLoader?, stats?,
&gt; target?, watch?, watchOptions? }    For typos: please correct them.   
&gt; For loader options: webpack 2 no longer allows custom properties in
&gt; configuration.
&gt;      Loaders should be updated to allow passing options via loader options in module.rules.
&gt;      Until loaders are updated one can use the LoaderOptionsPlugin to pass these options to the loader:
&gt;      plugins: [
&gt;        new webpack.LoaderOptionsPlugin({
&gt;          // test: /\.xxx$/, // may apply this only for some modules
&gt;          options: {
&gt;            postcss: ...
&gt;          }
&gt;        })
&gt;      ]
&gt;  - configuration.resolve has an unknown property &#39;root&#39;. These properties are valid:    object { alias?, aliasFields?,
&gt; cachePredicate?, descriptionFiles?, enforceExtension?,
&gt; enforceModuleExtension?, extensions?, fileSystem?, mainFields?,
&gt; mainFiles?, moduleExtensions?, modules?, plugins ?, resolver?,
&gt; symlinks?, unsafeCache?, useSyncFileSystemCalls? }
&gt;  - configuration.resolve.extensions[0] should not be empty.

My webpack file is:

    // work with all paths in a cross-platform manner
    const path = require(&#39;path&#39;);
    
    // plugins covered below
    const { ProvidePlugin } = require(&#39;webpack&#39;);
    const CopyWebpackPlugin = require(&#39;copy-webpack-plugin&#39;);
    const HtmlWebpackPlugin = require(&#39;html-webpack-plugin&#39;);
    
    // configure source and distribution folder paths
    const srcFolder = &#39;src&#39;;
    const distFolder = &#39;dist&#39;;
    
    // merge the common configuration with the environment specific configuration
    module.exports = {
    
        // entry point for application
        entry: {
            &#39;app&#39;: path.join(__dirname, srcFolder, &#39;ts&#39;, &#39;app.tsx&#39;)
        },
    
        // allows us to require modules using
        // import { someExport } from &#39;./my-module&#39;;
        // instead of
        // import { someExport } from &#39;./my-module.ts&#39;;
        // with the extensions in the list, the extension can be omitted from the 
        // import from path
        resolve: {
            // order matters, resolves left to right
            extensions: [&#39;&#39;, &#39;.js&#39;, &#39;.ts&#39;, &#39;.tsx&#39;, &#39;.json&#39;],
            // root is an absolute path to the folder containing our application 
            // modules
            root: path.join(__dirname, srcFolder, &#39;ts&#39;)
        },
    
        module: {
            loaders: [
                // process all TypeScript files (ts and tsx) through the TypeScript 
                // preprocessor
                { test: /\.tsx?$/,loader: &#39;ts-loader&#39; },
                // processes JSON files, useful for config files and mock data
                { test: /\.json$/, loader: &#39;json&#39; },
                // transpiles global SCSS stylesheets
                // loader order is executed right to left
                {
                    test: /\.scss$/,
                    exclude: [path.join(__dirname, srcFolder, &#39;ts&#39;)],
                    loaders: [&#39;style&#39;, &#39;css&#39;, &#39;postcss&#39;, &#39;sass&#39;]
                },
                // process Bootstrap SCSS files
                {
                    test: /\.scss$/,
                    exclude: [path.join(__dirname, srcFolder, &#39;scss&#39;)],
                    loaders: [&#39;raw&#39;, &#39;sass&#39;]
                }
            ]
        },
    
        // configuration for the postcss loader which modifies CSS after
        // processing
        // autoprefixer plugin for postcss adds vendor specific prefixing for
        // non-standard or experimental css properties
        postcss: [ require(&#39;autoprefixer&#39;) ],
    
        plugins: [
            // provides Promise and fetch API for browsers which do not support
            // them
            new ProvidePlugin({
                &#39;Promise&#39;: &#39;es6-promise&#39;,
                &#39;fetch&#39;: &#39;imports?this=&gt;global!exports?global.fetch!whatwg-fetch&#39;
            }),
            // copies image files directly when they are changed
            new CopyWebpackPlugin([{
                from: path.join(srcFolder, &#39;images&#39;),
                to: path.join(&#39;..&#39;, &#39;images&#39;)
            }]),
            // copies the index.html file, and injects a reference to the output JS 
            // file, app.js
            new HtmlWebpackPlugin({
                template: path.join(__dirname, srcFolder, &#39;index.html&#39;),
                filename:  path.join(&#39;..&#39;, &#39;index.html&#39;),
                inject: &#39;body&#39;,
            })
        ],
    
        // output file settings
        // path points to web server content folder where the web server will serve 
        // the files from file name is the name of the files, where [name] is the 
        // name of each entry point	
        output: {
            path: path.join(__dirname, distFolder, &#39;js&#39;),
            filename: &#39;[name].js&#39;,
            publicPath: &#39;/js&#39;
        },
    
        // use full source maps
        // this specific setting value is required to set breakpoints in they
        // TypeScript source in the web browser for development other source map
        devtool: &#39;source-map&#39;,
    
        // use the webpack dev server to serve up the web application
        devServer: {
            // files are served from this folder
            contentBase: &#39;dist&#39;,
            // support HTML5 History API for react router
            historyApiFallback: true,
            // listen to port 5000, change this to another port if another server 
            // is already listening on this port
            port: 5000,
            // proxy requests to the JSON server REST service
            proxy: {
                &#39;/widgets&#39;: {
                    // server to proxy
                    target: &#39;http://0.0.0.0:3010&#39;
                }
            }
        }
    
    };



Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema

I am using TypeScript Version 2 for an Angular 2 component code.

I am getting error &quot;Property &#39;value&#39; does not exist on type &#39;EventTarget&#39;&quot; for below code, what could be the solution. Thanks!

`e.target.value.match(/\S+/g) || []).length`

```js
import { Component, EventEmitter, Output } from &#39;@angular/core&#39;;

@Component({
  selector: &#39;text-editor&#39;,
  template: `
    &lt;textarea (keyup)=&quot;emitWordCount($event)&quot;&gt;&lt;/textarea&gt;
  `
})
export class TextEditorComponent {
  @Output() countUpdate = new EventEmitter&lt;number&gt;();

  emitWordCount(e: Event) {
    this.countUpdate.emit(
            (e.target.value.match(/\S+/g) || []).length);
  }
}
```

Property &#39;value&#39; does not exist on type &#39;EventTarget&#39;

What is the correct type for React events. Initially I just used `any` for the sake of simplicity. Now, I am trying to clean things up and avoid use of `any` completely.

So in a simple form like this:

    export interface LoginProps {
      login: {
        [k: string]: string | Function
        uname: string
        passw: string
        logIn: Function
      }
    }
    @inject(&#39;login&#39;) @observer
    export class Login extends Component&lt;LoginProps, {}&gt; {
      update = (e: React.SyntheticEvent&lt;EventTarget&gt;): void =&gt; {
        this.props.login[e.target.name] = e.target.value
      }
      submit = (e: any): void =&gt; {
        this.props.login.logIn()
        e.preventDefault()
      }
      render() {
        const { uname, passw } = this.props.login
        return (
          &lt;div id=&#39;login&#39; &gt;
            &lt;form&gt;
              &lt;input
                placeholder=&#39;Username&#39;
                type=&quot;text&quot;
                name=&#39;uname&#39;
                value={uname}
                onChange={this.update}
              /&gt;
              &lt;input
                placeholder=&#39;Password&#39;
                type=&quot;password&quot;
                name=&#39;passw&#39;
                value={passw}
                onChange={this.update}
              /&gt;
              &lt;button type=&quot;submit&quot; onClick={this.submit} &gt;
                Submit
              &lt;/button&gt;
            &lt;/form&gt;
          &lt;/div&gt;
        )
      }
    }


What type do I use here as event type?

`React.SyntheticEvent&lt;EventTarget&gt;` does not seem to be working as I get an error that `name` and `value` do not exist on `target`.

More generalised answer for all events would be really appreciated.

Thanks

Content Type	Original Author	Original Content on Stackoverflow
Question	Wink Saville	View Question on Stackoverflow
Solution 1 - node.js	千木郷	View Answer on Stackoverflow

Relationship between the version of node.js and the version of @types/node

node.js Problem Overview

node.js Solutions

Solution 1 - node.js

Visual Studio 2015 How to merge a branch into master?

How can I style active Link in react-router v4?

Attributions