nwutils / nw-builder Goto Github PK
View Code? Open in Web Editor NEWBuild NW.js applications for Linux, MacOS and Windows
License: MIT License
Build NW.js applications for Linux, MacOS and Windows
License: MIT License
Downloads don't work from behind a corporate firewall.
I made two changes:
And it works. (setting rq.proxy to true allows request to use process.env.HTTP_PROXY et al if available).
I can only test on a Win 7 machine behind the firewall.
(I'm willing to submit a pull request, but my ability to test on different platforms is limited.)
Hello,
What am I doing wrong with this? I've tried two approaches:
gulpfile.js:
// Load the required modules
var gulp = require('gulp');
var nib = require('nib');
var stylus = require('gulp-stylus');
var NwBuilder = require('node-webkit-builder');
gulp.task('stylus', function () {
gulp.src('./src/app/styl/app.styl')
.pipe(stylus({
use: [nib()],
compress: true
}))
.pipe(gulp.dest('./src/app/css'));
});
gulp.task('nw', ['stylus'], function () {
gulp.src( ['./src/**', './node_modules/**', '!./node_modules/gulp*/**', './package.json', './README.md', './LICENSE.txt' ])
.pipe(NwBuilder({
version: '0.9.2',
platforms: [ 'win', 'osx', 'linux32', 'linux64' ],
macIcns: './images/appicon.icns',
appName: 'App Name'
}))
.pipe(gulp.dest('./build'));
});
gulp.task('nodewebkit', ['stulys'], function () {
var nw = new NwBuilder({
version: '0.9.2',
files: [ './src/**', './node_modules/**', '!./node_modules/gulp*/**', './package.json', './README.md', './LICENSE.txt' ],
platforms: [ 'win', 'osx', 'linux32', 'linux64' ],
macIcns: './images/appicon.icns',
appName: 'App Name'
});
// Log stuff you want
nw.on('log', console.log);
// Build retruns a promise
nw.build().then(function () {
console.log('all done!');
}).catch(function (error) {
console.error(error);
});
});
gulp.task('default', ['stylus']);
gulp.task('css', ['stylus']);
I am fairly new to both Node & Gulp, but I am eager to learn! Please, if anyone can see my logic, please help me in the right direction. Any help is really appreciated!
quite
should be quiet
also, there are a few more "plattform" spellings of "platform" (one in the readme and 3 in bin/nwbuild)
๐ค good night ๐ โต ๐จ
node-webkit apps are now required to be shipped with locales folder for Windows and Linux 0.10.* or over, otherwise 'navigator.language' becomes empty and fails to detect OS language.
Sorry, I have no time to create PR now but hope this information helps.
nwjs/nw.js#2031
FYI, we have temporarily made a quick fix to add another Grunt task to copy locales dir but this can be done on node-webkit-builder side.
Was fine with 0.8.6, switched to building for 0.10.5, then got this:
events.js:72
throw er; // Unhandled 'error' event
^
Error: EISDIR, open 'E:\...\cache\0.10.5\linux32\locales'
I've tried deleting the cache directory beforehand, doesn't help. Works when building just for Mac & Windows.
Hi,
I get the following error when trying to build with nwbuild:
{ [RangeError: Maximum call stack size exceeded]
errno: 47,
code: 'EEXIST',
path: '',
syscall: 'mkdir' }
It seems to work fine when dragging my folder onto nw.exe. Any ideas what is causing this?
Thanks,
-John
Because of nwjs/nw.js#2390, I'm now wondering if it handy if we allow the user to specify platform-specific exceptions in the app manifest; e.g. a user that frame
is true
for Mac but false
for everything else.
node-webkit-builder would have to copy over the manifest somewhere and create a new copy per platform, then run a separate build on each.
Thoughts?
Im getting the following error when i try to run:
~/code/nodewebkit/nodewebkit-angular-sass-grunt-example (763): grunt build
Running "nodewebkit:src" (nodewebkit) task
Downloading: http://dl.node-webkit.org/v0.0.1/node-webkit-v0.0.1-win-ia32.zip
Downloading: http://dl.node-webkit.org/v0.0.1/node-webkit-v0.0.1-osx-ia32.zip
Unzipping: .../nodewebkit/nodewebkit-angular-sass-grunt-example/dist/cache/win/0.0.1/node-webkit-v0.0.1-win-ia32.zip
Fatal error: ZIP end of central directory record signature invalid (expects 0x06054b50, actually 0x4f44213c)
This is how my grunt fconfig looks:
nodewebkit: {
options: {
build_dir: './dist', // Where the build version of my node-webkit app is saved
mac: true, // We want to build it for mac
win: true, // We want to build it for win
linux32: false, // We don't need linux32
linux64: false, // We don't need linux64
//download_url: 'http://www.soundnodeapp.com/build/',
//mac_icns: './app/soundnode.icns',
version: '0.0.1'
},
src: [
'./app//*'
//'!./app/public/stylesheets/sass',
//'!./app/public/stylesheets/config.rb',
//'!.//*.sass-cache',
//'!./app/public/assets'
]
},
What is wrong heeler, the error message tells me nothing.
./[...]: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory
I get above error message. Are the builds incomplete?
I've just tried to upgrade to using the latest Node-Webkit build (0.10.2) and am having trouble building it in Grunt.
It downloads the correct version and reports it as unzipping but after that it seems to stop. The file list in the webkitFiles array don't seem to match what is in the ZIP (icudtl.dll seems to be icudtl.dat now).
Trying again with 0.10.0 seems to stop at the unzipping step too.
My Grunt definition is:
nodewebkit: {
options: {
version : '0.10.0',
build_dir: buildPath, // Where the build version of my node-webkit app is saved
credits : '', // html file to show in About screen
mac_icns : './example/icon.icns', // Path to the Mac icon file
mac : true, // We want to build it for mac
win : true, // We want to build it for win
linux32 : false, // We don't need linux32
linux64 : false // We don't need linux64
},
src : buildPath + '/**/*' // Your node-webkit app
}
Is this a known issue with this latest version or am I facing a different issue?
Thanks!
When I set the version to 0.10.0 (the latest), it strips out the last 0 and tries to download the wrong url.
Thanks.
After building my app, the Windows version works fine, but when I try to open the osx version (using open appName.app in terminal), I get "The application cannot be opened because its executable is missing."
I've looked at the Info.plist file, and it lists node-webkit as the executable. I found that file in appName.app/Contents/MacOS. Tried changing Info.plist to specify that path, but that didn't help.
Built via terminal on Mac, using "sudo nwbuild -p osx app.nw" (my app is in the app.nw directory).
To replace the windows icon, rcedit simply doesn't work as it generates the wrong icon resource headers resulting in ugly window icons. Using Resource Hacker with command line
ResHacker.exe -modify "Project.exe", "Project.exe", "ProgramIcon.ico", ICONGROUP, MAINICON, 0
Works perfectly generating the correct icon header and results in high quality icons.
Currently the "macZip: true" option seems to be broken as the generated Zip file is stored over the file "nw.icns" instead of creating a new file named "app.nw".
See line 346 in lib/index.js:
https://github.com/mllrsohn/node-webkit-builder/blob/master/lib/index.js#L346
Currently it reads:
copiedFiles.push(Utils.copyFile(self._nwFile, path.resolve(platform.releasePath,
self.options.appName+'.app', 'Contents', 'Resources', 'nw.icns')));
But it should read:
copiedFiles.push(Utils.copyFile(self._nwFile, path.resolve(platform.releasePath, self.options.appName+'.app', 'Contents', 'Resources', 'app.nw')));
Please fix this so the "macZip" option works as expected. Thanks.
The subject says it all. As Roger Wang says in https://groups.google.com/d/msg/node-webkit/zysKp3n37_4/b-B2O0rCF2gJ, the icudtl.dat file needs to be included in the build. If not, at least in Windows, the application does not run.
Thanks in advance for the update! Yours is a truly useful Grunt task.
It just creates a nw.exe
which shows "node-webkit" in ASCII art.
My usage:
var nwBuilder = new (require('node-webkit-builder'))({
files: './_public/**/**',
plattforms: ['win', 'osx'],
version: '0.9.2',
buildDir: './dist'
});
It is at least taking some information from dist/package.json
because in dist
there's a directory with the name
field as its name (and then a directory per platform inside, of course).
I've tried to set my app as the default app to open *.keeex
files in OSX and I configured the builder to change plist file (see below). Finally, when building I've got the error:
>> There was an Error: You have to set the appName and appVersion in the Plist options
What's wrong I had done?
Can someone provide an example for my case?
Thank you very much.
My configuration:
mac: {
options: {
version: '0.9.2',
platforms: ['osx'],
buildDir: './webkitbuilds',
macPlist: '<?xml version="1.0" encoding="UTF-8"?>' +
'<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">' +
'<plist version="1.0">' +
'<dict>' +
'<key>BuildMachineOSBuild</key>' +
'<string>12C3006</string>' +
'<key>CFBundleDevelopmentRegion</key>' +
'<string>en</string>' +
'<key>CFBundleDisplayName</key>' +
'<string>KeeeX</string>' +
'<key>CFBundleExecutable</key>' +
'<string>node-webkit</string>' +
'<key>CFBundleIconFile</key>' +
'<string>nw.icns</string>' +
'<key>CFBundleIdentifier</key>' +
'<string>com.intel.nw</string>' +
'<key>CFBundleInfoDictionaryVersion</key>' +
'<string>6.0</string>' +
'<key>CFBundleName</key>' +
'<string>KeeeX</string>' +
'<key>CFBundlePackageType</key>' +
'<string>APPL</string>' +
'<key>CFBundleShortVersionString</key>' +
'<string>Version lydig-1.0</string>' +
'<key>CFBundleVersion</key>' +
'<string>lydig-1.0</string>' +
'<key>DTSDKBuild</key>' +
'<string>11E52</string>' +
'<key>DTSDKName</key>' +
'<string>macosx10.7</string>' +
'<key>DTXcode</key>' +
'<string>0452</string>' +
'<key>DTXcodeBuild</key>' +
'<string>4G2008a</string>' +
'<key>LSFileQuarantineEnabled</key>' +
'<true/>' +
'<key>LSMinimumSystemVersion</key>' +
'<string>10.6.0</string>' +
'<key>NSPrincipalClass</key>' +
'<string>NSApplication</string>' +
'<key>NSSupportsAutomaticGraphicsSwitching</key>' +
'<true/>' +
'<key>SCMRevision</key>' +
'<string>239963</string>' +
'<key>CFBundleDocumentTypes</key>' +
'<array>' +
'<dict>' +
'<key>CFBundleTypeName</key>' +
'<string>keeex</string>' +
'<key>CFBundleTypeIconFile</key>' +
'<string>nw.icns</string>' +
'<key>LSHandlerRank</key>' +
'<string>Owner</string>' +
'<key>LSItemContentTypes</key>' +
'<array>' +
'<string>com.keeex.keeex</string>' +
'/array>' +
'/dict>' +
'/array>' +
'<key>UTExportedTypeDeclarations</key>' +
'<array>' +
'<dict>' +
'<key>UTTypeConformsTo</key>' +
'<array>' +
'<string>public.data</string>' +
'/array>' +
'<key>UTTypeDescription</key>' +
'<string>KeeeX</string>' +
'<key>UTTypeIconFile</key>' +
'<string>nw.icns</string>' +
'<key>UTTypeIdentifier</key>' +
'<string>com.keeex.keeex</string>' +
'<key>UTTypeReferenceURL</key>' +
'<string>https://keeex.io</string>' +
'<key>UTTypeTagSpecification</key>' +
'<dict>' +
'<key>com.apple.ostype</key>' +
'<string>keeex</string>' +
'<key>public.filename-extension</key>' +
'<array>' +
'<string>keeex</string>' +
'/array>' +
'<key>public.mime-type</key>' +
'<string>application/octet-stream</string>' +
'/dict>' +
'/dict>' +
'/array>' +
'</dict>' +
'</plist>'
},
src: ['./dist/mac/**/*']
}
Code to recreate:
var NwBuilder = require('node-webkit-builder')
var nw = new NwBuilder({
files: './nwapp/**/**', // use the glob format
platforms: ['win','osx']
})
nw.run(cb)
when run on OSX results in:
events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn EACCES
at errnoException (child_process.js:998:11)
at Process.ChildProcess._handle.onexit (child_process.js:789:34)
when debugging the problem I discovered that its because the executable being run is nw.exe
this is because of the runApp() implementation (lib/index.js):
NwBuilder.prototype.runApp = function () {
var self = this,
platform = this._platforms[0], // <------ this is the problem
executable = path.resolve(platform.cache, platform.runable);
self.emit('log', 'Launching App');
return new Promise(function(resolve, reject) {
var p = spawn(executable, ['--enable-logging', self.options.files.replace(/\*[\/\*]*/,"")]);
p.stdout.on('data', function(data) {
self.emit('stdout', data);
});
p.stderr.on('data', function(data) {
self.emit('stderr', data);
});
p.on('close', function(code) {
self.emit('log', 'App exited with code ' + code);
resolve();
});
});
};
this doesn't happen when running from command line because (bin/nwbuild):
// Check Plattform, if we are in run mode
if(argv.r) {
switch(process.platform) {
case 'darwin':
options.platforms = ['osx'];
break;
case 'win32':
options.platforms = ['win'];
break;
case 'linux':
options.platforms = [(process.arch === 'x64' ? 'linux64' : 'linux32')];
break;
default:
console.log('Unable to run app - plattform is not supported');
process.exit(0);
break;
}
}
which cause _platforms to contain only 1 platform
PR will follow...
Using v0.10.
Create cache folder in C:\workspace\craftyjs\cache\0.10.
Downloading: http://dl.node-webkit.org/v0.10./node-webkit-v0.10.-win-ia32.zip
Create cache folder in C:\workspace\craftyjs\cache\0.10.
Downloading: http://dl.node-webkit.org/v0.10./node-webkit-v0.10.-osx-ia32.zip
I've added this functionality here: 1j01@b0d35f2 but without any tests or anything. Also "really" it should be added to a new NwRunner.
So that we can just write up an npm script for building instead of using Grunt/Gulp or the programmatic API.
Hi
Currently all files in app/plugin
folder are are copied to all different builds. Instead it should only copy the plugin files relevant to the platform. Currently i am shipping my builds (mac/windows
) with flashplayer (Flash Player.plugin & pepflashplayer.dll
). when running the deploy build, i got these both the files copied to both the builds. This is unnecessary, and end up taking more space than expected.
Is there any way to copy the plugin files on conditional basis?. If there isn't any existing approach, i would like to make a patch?
Please let me know
Since I don't really have time to finish this at the moment and a couple of people are using it it would be great if somebody would take lead on this and do the following tasks:
If you feel up for the tasks I'll give your write permissions to the repo and to npm.
build()
promise:
nwbuild({
files: "src/**/**"
})
.catch(callback)
.then(callback);
callback:
nwbuild({
files: "src/**/**"
},
function(error) {
if (error) throw error;
});
build()
arguments[1]
promise:
nwbuilder.build({
files: "src/**/**"
})
.catch(callback)
.then(callback);
callback:
nwbuilder.build({
files: "src/**/**"
},
function(error) {
if (error) throw error;
});
When I run the node-webkit-builder, I get the following error
events.js:72
throw er; // Unhandled 'error' event
^
Error: EMFILE, open '/Users/robin/project/xxxxxxx--xxxx.js'
Warning: -> error 8 /Users/robin/project/xx---xxxxxxxxx.js (1671ms) Use --force to continue.
Aborted due to warnings.
I initially thought that its because of too many files in my project, but I still get this even if I reduce the number of files in my project significantly.
Surprising it works when I run it through terminal of my Intellij. This sounds too weird to me also.
Description:
Stopped working (wow thanks)
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: resourcer.exe
Problem Signature 02: 0.9.3531.38736
Problem Signature 03: 4a9d92b4
Problem Signature 04: mscorlib
Problem Signature 05: 2.0.0.0
Problem Signature 06: 530eec86
Problem Signature 07: 34a9
Problem Signature 08: 119
Problem Signature 09: System.IO.DirectoryNotFound
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
bla bla bla
Update executable icon
close program
Unhandled Exception: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\Isaiah\AppData\Local\Anolis\Exceptions.log'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions o
ptions, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean
bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
at System.IO.StreamWriter..ctor(String path, Boolean append)
at Anolis.Resourcer.Program.Main(String[] args)
Error while updating the Windows icon.
Gives you some kind of error about the version, while what it should do is implement a check whether or not it can fetch the resource from the server.
Passing a winIco
breaks things. I get the dummy "node webkit" (in ascii art) app. macIcns
works fine.
You can lighten your code by using download instead of request+progress.
If you try to download a version that isn't there (which happens by default now, fixed by #27 ), the download failing does not report an error. Instead, the zlib module errors out while trying to gunzip the package which gives this cryptic error message from bluebird.
~/node-webkit-test/node_modules/node-webkit-builder/node_modules/bluebird/js/main/promise_resolver.js:119
throw new TypeError("Illegal invocation, resolver resolve/reject must
^
TypeError: Illegal invocation, resolver resolve/reject must be called within a resolver context. Consider using the promise constructor instead.
at Gunzip.PromiseResolver$reject (~/node-webkit-test/node_modules/node-webkit-builder/node_modules/bluebird/js/main/promise_resolver.js:119:15)
at Gunzip.emit (events.js:117:20)
at Zlib._binding.onerror (zlib.js:298:10)
Instead, the download should properly fail by listening to the 'error'
event from request. I'm not sure about the bluebird error, but I think it has to do with the call to Promise#reject
in the wrong context.
There's no error, it just sits at 1%
Here's a screenshot where it has downloaded the osx version, but won't download the windows version, so it sits at about 50%
It might be only the windows version that it sometimes fails to download but I'm not sure.
It usually works the second time.
#66 could fix this.
https://gist.github.com/jtenner/32361f8df3c291faa731
Refrenced the gist here. Windows executable doesn't start up index.html and sits on nw:blank when i start the application.
Any help?
(Manually specifying a version works.)
Latest Version: v0.10.1-1
Using v0.10.1-1
Create cache folder in C:\Users\Isaiah\Code\GitHub\node-webkit-builder\cache\0.10.1-1
Downloading: http://dl.node-webkit.org/v0.10.1-1/node-webkit-v0.10.1-1-win-ia32.zip
ERROR: The version 0.10.1-1 does not have a corresponding build posted at http://dl.node-webkit.org/. Please choose a version from that list.
Unable to download nodewebkit.
The package nodewebkit is at 0.10.1-1
so it tries to dl 0.10.1-1
whereas http://dl.node-webkit.org/ has v0.10.2
, which it ought to somehow find.
Should this be taken up as an issue on https://github.com/shama/nodewebkit to release v0.10.2
? Why are we taking the versions from "An installer for node-webkit"? Scraping seems more reliable, as long as http://dl.node-webkit.org/ stays as an index listing.
At any rate, we can't expect the package not to have intermediate versions. Maybe we should just strip out the dash part.
Hey,
I'm on kubuntu 13.10 here. Nwbuild doesn't fetch the latest node-webkit version.
Running nwbuild for any of the platforms gives me the following output:
Using v0.9.1
Create cache folder in /usr/local/lib/node_modules/node-webkit-builder/cache/0.9.1
Using cache for: linux32
Launching App
App exited with code 2
I always get the libudev missing error (https://github.com/rogerwang/node-webkit/wiki/The-solution-of-lacking-libudev.so.0), so the exited with code 2 might just be that with a useless error message since it's an older nw version.
Cheers
... for specifying an app icon. GNOME and KDE both support PNG and SVG files for icons.
http://standards.freedesktop.org/desktop-entry-spec/latest/index.html
The builder work fine (in windows) until i add the winIco in the options. The icon changes but when i run the program all i get is a node-webkit default window.
I've tried to add the icon with resource hacker and the program works with the new icon
Config:
nodewebkit: {
options: {
version: '0.10.0-rc1',
build_dir: './build',
app_version: '0.0.1',
keep_nw: true,
zip: false,
mac: true,
win: false,
linux32: false,
linux64: false
},
src: ['public/**/*.*'] // Your node-webkit app
}
When build on mac, the generated app cannot be launched. When building same thing on 0.9.2 it works fine.
Get this EISDIR error when trying to build my app for linux64:
It only happens with v0.10.2 (0.10.1 worked fine) and if linux is included in the platforms array. Here's options I pass (except version
, they didn't change since 0.10.1):
nodewebkit: {
dist: {
options: {
version: '0.10.2',
platforms: ['win', 'osx', 'linux32', 'linux64'],
appName: 'App',
appVersion: '<%= pkg.version %>',
distDir: 'build/',
cacheDir: 'build/cache/',
macCredits: 'support/Credits.html',
macIcns: 'support/app.icns'
},
src: ['<%= distDir %>/**']
}
}
What would cause a nw.exe
to open on the dummy page with the ascii art? How can I troubleshoot it?
I've seen it a good few times before. Right now it's happening consistently. I can build for Mac on any platform without problems, but if I build for Windows (on Windows / Mac) it'll build fine but when ran it shows the ascii art screen. To be clear, I've even built the app on a Mac and transferred the files to a Windows machine. I've tried multiple Windows machines.
The exe
looks the right size and if I rename it to nw.zip
& extract, then it seems all my files are there.
Description says this:
It will download the prebuilt binaries for a newest version, unpacks it, creates a release folder, create the app.nw file for a specified directory and copies the app.nw file where it belongs.
Does that mean that a binary is made by downloading node-webkit and packaging it as part of the release binary. OR does this mean that the binary itself, when installed on an end-user's computer, will download the prebuilt node-webkit binary? And if it doesn't do the second, could it? (As that would be really awesome.)
referencing from the grunt plugin:
Can't run nwbuild
It returns env: node\r: No such file or directory with every execution
nwbuild -r .
env: node\r: No such file or directory
nwbuild -h
env: node\r: No such file or directory
I need to pack a custom built ffmpegsumo.dll
(win), ffmpegsumo.so
(osx) and libffmpegsumo.so
(linux).
Is there a way to do so using this module?
Hi there,
I've compiled an app for all OS from a Mac.
For Mac, everything is allright. For Windows, the app is working fine except for window features: closing or minimizing the app is not possible (using node webkit API)...
I've searched a bit but I found nothing about a similar issue. Any idea?
By the way, your tool is fantastic :) it saves me so much time!
So, subj. For now we have ia32 only.
Thanks for this program! It has made working with node-webkit a bit easier.
I'd like to suggest that the generated files take on the application's name. In particular: nw
on linux, node-webkit.app
on osx and nw.exe
on windows. If you're for it, I'll submit a PR, but It's a bit awkward to have this generate the specified names without knowing that's what's going to happen. From the README, it seems that the name supplied (or the one in the package.json) would be the name of the application when it was generated. You could still default it to the original names if not supplied anything. I've not found anything that states this isn't possible, and from testing, renaming seems to work on all os's.
Is there any reason why this isn't/can't be supported? If not, expect a PR soon.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.