ray007

That's all nice, but when it's not compatible with any MessageFormat anymore it should get a new name. Adding a `2` at the end is not enough and might mislead...

If it can use the old MF1 syntax without changes, then yes, but I'd call it "legacy support" or something like that. But with the new syntax being different (and...

@phated Yes, the file does exist, I even get a command-line tab completion for it. The error above also happens since I directly supply the path to 1 file without...

Note: for `gulp.dest()` a UNC path does work. Guess that means the `glob` module is somehow to blame for this.

I've already tried this interactive in the node shell, and it does not work.

Update: ```js var glob = require('glob'); glob.sync('manual.doc', {cwd: //server.domain.name/share/some/folders}); ``` does work. But ```js function () { let sDir = '//server.domain.name/share/some/folders'; return gulp.src('manual.doc', {cwd: '//server.domain.name/share/some/folders'}) .pipe(...); } ``` does not....

It's unfortunate if `glob` does not fix the bug. But it is possible to work around the glob bug by not passing an absolute path, but setting the `cwd` option...

I did some debugging, and the problem seems to start in `glob-stream/readable.js`, when all globs are converted to absolute (line 61). Not even setting the `root` option does avoid this...

> > > @ray007 yeah, unfortunately making all paths absolute is a thing we **must** do. I forget exactly what it solves but it was something important. I cannot imagine...

It may well be the fault of nativescript somehow, but the fact remains that something must have changed in `js-base64` since the upgrade of this module only triggered the problem....