Relative same folder glob selector is not evaluated correctly

[JakubHlousek]

Environment

• OS Version: Windows 10 Home (21H2)
• Node.js Version: 8.15.1

Actual behaviour

When using a glob import syntax starting with ./ the relative path gets evaluated incorrectly

Example folder structure:
├── themes
│ ├── dark.theme.json
│ ├── light.theme.json
│ ├── contrast.theme.json
│ └── Themes.js <-- relative import from here
└── index.js

the following import

import * as ThemeObjects from "./*.theme.json

gets evaluated into

import * as module0 from 'dark.theme.json'
import * as module1 from 'light.theme.json'"
import * as module2 from 'contrast.theme.json'

which incorrectly refers to the root directory resulting in a crash

Expected behaviour

the mentioned import should get evaluated into:

import * as module0 from './dark.theme.json'
import * as module1 from './light.theme.json'"
import * as module2 from './contrast.theme.json'

Steps to reproduce

Use a relative import to refer to contents in the same folder

Possible fix

After inspecting the source files I discovered a possible culprit:

fast-glob/src/providers/provider.ts

Line 26 in 79260ad

const basePath = task.base === '.' ? '' : task.base;

The conditional statement on this line destroys otherwise perfectly working import. Is this the intended behaviour?