Parser doesn't recognize flow comments with leading spaces

[vikr01]

Bug Report

Current Behavior

Using @babel/parser v7.2.0.

Flow comments are recognized as flow typings when they start with /*::, /*:, and /*flow-include, but when there's spaces it sees them as an ordinary comment (i.e. /* ::, /* : and /* flow-include).

Input Code

• try it on flow.org

/* @flow */

import React, { Component/* ::, type Node */ } from 'react';

/*                          	flow-include
type Foo = string;
*/

Expected behavior/code
Spaces after the start of the comment should be considered the same as no spaces with flow comments.

The behavior for newlines after the start of the comment shouldn't change though, as flow still sees those as comments, i.e.:

/*
:: type Foo = string; */ // <- This should be seen as a comment

/*  :: type Foo = string */ // <- This should be seen as a typing

[babel-bot]

Hey @vikr01! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
community that typically always has someone willing to help. You can sign-up here
for an invite.