Support GH pages, build with gulp

[vgrichina]

Main selling point is that npm run deploy build and deploys everything.

[evgenykuzyakov]

Is there are a better option than a hard copy for assembly-json and near-runtime-ts files?

[vgrichina]

@evgenykuzyakov waiting for AssemblyScript/assemblyscript#448 to land.

Probably can also hack it myself on a level of overriding readFile (similar to how can now read modules from out/ folder without copy necessary).

[evgenykuzyakov]

I'm fine with copying from blank_project. I just don't want us to have a copy in this repo.

[janedegtiareva]

nit: I liked the test environment better under src, to not pollute the top level dir

[vgrichina]

@janedegtiareva it's used from near-shell node module (i.e. it's not present in project template at all anymore).

[janedegtiareva]

It's a good file to have in the project template to allow devs to modify the default behaviour.

[vgrichina]

ah, I see, there is some app-specific stuff

It looks like files are largely identical though, except nodeUrl. So I think probably best would be to load this stuff from env-specific config and then have common test env use project-specific config.

[janedegtiareva]

Some sort of base makes sense

[vgrichina]

Leaving as is for this PR, gonna clean-up as part of #21

[janedegtiareva]

@evgenykuzyakov waiting for AssemblyScript/assemblyscript#448 to land.

Probably can also hack it myself on a level of overriding readFile (similar to how can now read modules from out/ folder without copy necessary).

The near build command handled this without hardcoding. Can we at least use that solution?

[vgrichina]

@evgenykuzyakov waiting for AssemblyScript/assemblyscript#448 to land.
Probably can also hack it myself on a level of overriding readFile (similar to how can now read modules from out/ folder without copy necessary).

The near build command handled this without hardcoding. Can we at least use that solution?

It's not compatible with NEARStudio. Not sure what do you mean by "near build command handled this without hardcoding". Wasn't it merely copying files from hard-coded locations?

	  await copyFileFn("./node_modules/near-runtime-ts/near.ts", yargs.argv.out_dir + "/near.ts");
	  await ensureDir(yargs.argv.out_dir + "/json");
	  await copyFileFn("./node_modules/assemblyscript-json/assembly/encoder.ts", yargs.argv.out_dir + "/json/encoder.ts");
	  await copyFileFn("./node_modules/assemblyscript-json/assembly/decoder.ts", yargs.argv.out_dir + "/json/decoder.ts");	

It's pretty trivial to add this hardcoded mapping on readFile handler level as well, just not clear where to take these files in Studio (cause there is no solution yet to load modules from package.json into studio).

[vgrichina]

GitLab failure gonna be resolved after merge (cause build depends on stuff not merged yet).