GithubHelp home page GithubHelp logo

jspm-react's Introduction

Jekyll Now

Jekyll is a static site generator that's perfect for GitHub hosted blogs (Jekyll Repository)

Jekyll Now makes it easier to create your Jekyll blog, by eliminating a lot of the up front setup.

  • You don't need to touch the command line
  • You don't need to install/configure ruby, rvm/rbenv, ruby gems ☺️
  • You don't need to install runtime dependancies like markdown processors, Pygments, etc
  • If you're on Windows, this will make setting up Jekyll a lot easier
  • It's easy to try out, you can just delete your forked repository if you don't like it

In a few minutes you'll be set up with a minimal, responsive blog like the one below giving you more time to spend on writing epic blog posts!

Jekyll Now Theme Screenshot

Quick Start

Step 1) Fork Jekyll Now to your User Repository

Fork this repo, then rename the repository to yourgithubusername.github.io.

Your Jekyll blog will often be viewable immediately at http://yourgithubusername.github.io (if it's not, you can often force it to build by completing step 2)

Step 1

Step 2) Customize and view your site

Enter your site name, description, avatar and many other options by editing the _config.yml file. You can easily turn on Google Analytics tracking, Disqus commenting and social icons here too.

Making a change to _config.yml (or any file in your repository) will force GitHub Pages to rebuild your site with jekyll. Your rebuilt site will be viewable a few seconds later at http://yourgithubusername.github.io - if not, give it ten minutes as GitHub suggests and it'll appear soon

There are 3 different ways that you can make changes to your blog's files:

  1. Edit files within your new username.github.io repository in the browser at GitHub.com (shown below).
  2. Use a third party GitHub content editor, like Prose by Development Seed. It's optimized for use with Jekyll making markdown editing, writing drafts, and uploading images really easy.
  3. Clone down your repository and make updates locally, then push them to your GitHub repository.

_config.yml

Step 3) Publish your first blog post

Edit /_posts/2014-3-3-Hello-World.md to publish your first blog post. This Markdown Cheatsheet might come in handy.

First Post

You can add additional posts in the browser on GitHub.com too! Just hit the + icon in /_posts/ to create new content. Just make sure to include the front-matter block at the top of each new blog post and make sure the post's filename is in this format: year-month-day-title.md

Local Development

  1. Install Jekyll and plug-ins in one fell swoop. gem install github-pages This mirrors the plug-ins used by GitHub Pages on your local machine including Jekyll, Sass, etc.
  2. Clone down your fork git clone [email protected]:yourusername/yourusername.github.io.git
  3. Serve the site and watch for markup/sass changes jekyll serve
  4. View your website at http://0.0.0.0:4000
  5. Commit any changes and push everything to the master branch of your GitHub user repository. GitHub Pages will then rebuild and serve your website.

Moar!

I've created a more detailed walkthrough, Build A Blog With Jekyll And GitHub Pages over at the Smashing Magazine website. Check it out if you'd like a more detailed walkthrough and some background on Jekyll. 🤘

It covers:

  • A more detailed walkthrough of setting up your Jekyll blog
  • Common issues that you might encounter while using Jekyll
  • Importing from Wordpress, using your own domain name, and blogging in your favorite editor
  • Theming in Jekyll, with Liquid templating examples
  • A quick look at Jekyll 2.0’s new features, including Sass/Coffeescript support and Collections

Jekyll Now Features

✓ Command-line free fork-first workflow, using GitHub.com to create, customize and post to your blog
✓ Fully responsive and mobile optimized base theme (Theme Demo)
✓ Sass/Coffeescript support using Jekyll 2.0
✓ Free hosting on your GitHub Pages user site
✓ Markdown blogging
✓ Syntax highlighting
✓ Disqus commenting
✓ Google Analytics integration
✓ SVG social icons for your footer
✓ 3 http requests, including your avatar

✘ No installing dependancies
✘ No need to set up local development
✘ No configuring plugins
✘ No need to spend time on theming
✘ More time to code other things ... wait ✓!

Questions?

Open an Issue and let's chat!

Other forkable themes

You can use the Quick Start workflow with other themes that are set up to be forked too! Here are some of my favorites:

Credits

Contributing

Issues and Pull Requests are greatly appreciated. If you've never contributed to an open source project before I'm more than happy to walk you through how to create a pull request.

You can start by opening an issue describing the problem that you're looking to resolve and we'll go from there.

I want to keep Jekyll Now as minimal as possible. Every line of code should be one that's useful to 90% of the people using it. Please bear that in mind when submitting feature requests. If it's not something that most people will use, it probably won't get merged. 💂‍♂️

jspm-react's People

Contributors

asaf avatar benglass avatar bmcorser avatar casesandberg avatar nickytonline avatar scott-coates avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

jspm-react's Issues

`gulp dist` raises an error

jspm-react[master] $ gulp dist
[15:34:48] Using gulpfile ~/Desktop/jspm-react/gulpfile.js
[15:34:49] Starting 'dist'...
[15:34:49] Starting 'delete-dist'...
[15:34:49] Finished 'delete-dist' after 8.25 ms
[15:34:49] Starting 'js'...
[15:34:49] Starting 'sass'...
[15:34:49] Finished 'dist' after 599 ms
[15:34:49] null
[15:34:49] Finished 'sass' after 630 ms
[15:34:49] Finished 'js' after 729 ms
[15:34:49] Starting 'build'...
[15:34:49] Finished 'build' after 4.98 μs
[15:34:49] Starting 'css'...
[15:34:49] Starting 'html'...
[15:34:49] Finished 'html' after 1.9 ms
[15:34:49] Starting 'js'...
[15:34:49] Finished 'js' after 28 ms
[15:34:49] Starting 'bundle'...
[15:34:49] Finished 'css' after 200 ms
     Building the single-file sfx bundle for build/js/main.js!jsx...

err  TypeError: Cannot read property 'suppressDeprecationMessages' of undefined
         at Logger.deprecate (file:/Users/Michael/Desktop/jspm-react/jspm_packages/npm/[email protected]/browser.js:8889:24)
         at File.normalizeOptions (file:/Users/Michael/Desktop/jspm-react/jspm_packages/npm/[email protected]/browser.js:8271:18)
         at new File (file:/Users/Michael/Desktop/jspm-react/jspm_packages/npm/[email protected]/browser.js:8237:22)
         at TransformerPipeline.transform (file:/Users/Michael/Desktop/jspm-react/jspm_packages/npm/[email protected]/browser.js:12107:16)
         at /usr/local/lib/node_modules/jspm/node_modules/systemjs-builder/compilers/es6.js:125:31
         at tryCatchReject (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:1183:30)
         at runContinuation1 (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:1142:4)
         at Fulfilled.when (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:930:4)
         at Pending.run (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:821:13)
         at Scheduler._drain (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:97:19)
         at Scheduler.drain (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:62:9)
[15:34:55] 'bundle' errored after 5.89 s
[15:34:55] Error in plugin 'gulp-shell'
Message:
    Command failed: /bin/sh -c jspm bundle-sfx build/js/main.js!jsx dist/js/app.js

Details:
    killed: false
    code: 1
    signal: null
    cmd: /bin/sh -c jspm bundle-sfx build/js/main.js!jsx dist/js/app.js
    stdout:      Building the single-file sfx bundle for build/js/main.js!jsx...

err  TypeError: Cannot read property 'suppressDeprecationMessages' of undefined
         at Logger.deprecate (file:/Users/Michael/Desktop/jspm-react/jspm_packages/npm/[email protected]/browser.js:8889:24)
         at File.normalizeOptions (file:/Users/Michael/Desktop/jspm-react/jspm_packages/npm/[email protected]/browser.js:8271:18)
         at new File (file:/Users/Michael/Desktop/jspm-react/jspm_packages/npm/[email protected]/browser.js:8237:22)
         at TransformerPipeline.transform (file:/Users/Michael/Desktop/jspm-react/jspm_packages/npm/[email protected]/browser.js:12107:16)
         at /usr/local/lib/node_modules/jspm/node_modules/systemjs-builder/compilers/es6.js:125:31
         at tryCatchReject (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:1183:30)
         at runContinuation1 (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:1142:4)
         at Fulfilled.when (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:930:4)
         at Pending.run (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:821:13)
         at Scheduler._drain (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:97:19)
         at Scheduler.drain (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:62:9)

    stderr:
Error running task sequence: { task: 'bundle',
  message: 'bundle stream',
  duration: 5.894989118,
  hrDuration: [ 5, 894989118 ],
  err:
   { [Error: Command failed: /bin/sh -c jspm bundle-sfx build/js/main.js!jsx dist/js/app.js
   ]
     killed: false,
     code: 1,
     signal: null,
     cmd: '/bin/sh -c jspm bundle-sfx build/js/main.js!jsx dist/js/app.js',
     stdout: '     Building the single-file sfx bundle for build/js/main.js!jsx...\n\nerr  TypeError: Cannot read property \'suppressDeprecationMessages\' of undefined\n         at Logger.deprecate (file:/Users/Michael/Desktop/jspm-react/jspm_packages/npm/[email protected]/browser.js:8889:24)\n         at File.normalizeOptions (file:/Users/Michael/Desktop/jspm-react/jspm_packages/npm/[email protected]/browser.js:8271:18)\n         at new File (file:/Users/Michael/Desktop/jspm-react/jspm_packages/npm/[email protected]/browser.js:8237:22)\n         at TransformerPipeline.transform (file:/Users/Michael/Desktop/jspm-react/jspm_packages/npm/[email protected]/browser.js:12107:16)\n         at /usr/local/lib/node_modules/jspm/node_modules/systemjs-builder/compilers/es6.js:125:31\n         at tryCatchReject (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:1183:30)\n         at runContinuation1 (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:1142:4)\n         at Fulfilled.when (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:930:4)\n         at Pending.run (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:821:13)\n         at Scheduler._drain (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:97:19)\n         at Scheduler.drain (/usr/local/lib/node_modules/jspm/node_modules/systemjs/node_modules/es6-module-loader/dist/es6-module-loader.src.js:62:9)\n',
     stderr: '',
     name: 'Error',
     message: 'Command failed: /bin/sh -c jspm bundle-sfx build/js/main.js!jsx dist/js/app.js\n',
     stack: 'Error: Command failed: /bin/sh -c jspm bundle-sfx build/js/main.js!jsx dist/js/app.js\n\n    at ChildProcess.exithandler (child_process.js:751:12)\n    at ChildProcess.emit (events.js:110:17)\n    at maybeClose (child_process.js:1015:16)\n    at Socket.<anonymous> (child_process.js:1183:11)\n    at Socket.emit (events.js:107:17)\n    at Pipe.close (net.js:485:12)',
     showStack: false,
     showProperties: true,
     plugin: 'gulp-shell' } }

What I did:

  • Clone the repo
  • Install jspm npm install -g jspm
  • Install gulp npm install -g gulp
  • npm install
  • jspm install
  • gulp dist

License

Can you put a license on this repo? I want to start working on some code for it!

libsass bindings not found

Using Node v4.1.1

$ gulp
/home/dave/code/jspm-react/node_modules/gulp-sass/node_modules/node-sass/lib/index.js:22
    throw new Error('`libsass` bindings not found. Try reinstalling `node-sass`?');
    ^

Error: `libsass` bindings not found. Try reinstalling `node-sass`?
    at getBinding (/home/dave/code/jspm-react/node_modules/gulp-sass/node_modules/node-sass/lib/index.js:22:11)
    at Object.<anonymous> (/home/dave/code/jspm-react/node_modules/gulp-sass/node_modules/node-sass/lib/index.js:188:23)
    at Module._compile (module.js:434:26)
    at Module._extensions..js (module.js:452:10)
    at Object.require.extensions.(anonymous function) [as .js] (/home/dave/code/jspm-react/node_modules/babel/node_modules/babel-core/lib/api/register/node.js:214:7)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/home/dave/code/jspm-react/node_modules/gulp-sass/index.js:3:17)

When trying to rebuild:

$ npm rebuild node-sass

> [email protected] install /home/dave/code/jspm-react/node_modules/node-sass
> node scripts/install.js


> [email protected] postinstall /home/dave/code/jspm-react/node_modules/node-sass
> node scripts/build.js

` /home/dave/code/jspm-react/node_modules/node-sass/vendor/linux-x64-46/binding.node ` exists. 
 testing binary.
Binary is fine; exiting.

> [email protected] install /home/dave/code/jspm-react/node_modules/gulp-sass/node_modules/node-sass
> node scripts/install.js


> [email protected] postinstall /home/dave/code/jspm-react/node_modules/gulp-sass/node_modules/node-sass
> node scripts/build.js

make: Entering directory '/home/dave/code/jspm-react/node_modules/gulp-sass/node_modules/node-sass/build'
  CXX(target) Release/obj.target/binding/src/binding.o
In file included from ../src/binding.cpp:1:0:
../node_modules/nan/nan.h:324:27: error: redefinition of ‘template<class T> v8::Local<T> Nan::imp::NanEnsureHandleOrPersistent(const v8::Local<T>&)’
   NAN_INLINE v8::Local<T> NanEnsureHandleOrPersistent(const v8::Local<T> &val) {
                           ^
../node_modules/nan/nan.h:319:17: note: ‘template<class T> v8::Handle<T> Nan::imp::NanEnsureHandleOrPersistent(v8::Handle<T>&)’ previously declared here
   v8::Handle<T> NanEnsureHandleOrPersistent(const v8::Handle<T> &val) {
                 ^
../node_modules/nan/nan.h:344:27: error: redefinition of ‘template<class T> v8::Local<T> Nan::imp::NanEnsureLocal(v8::Handle<T>&)’
   NAN_INLINE v8::Local<T> NanEnsureLocal(const v8::Handle<T> &val) {
                           ^
../node_modules/nan/nan.h:334:27: note: ‘template<class T> v8::Local<T> Nan::imp::NanEnsureLocal(const v8::Local<T>&)’ previously declared here
   NAN_INLINE v8::Local<T> NanEnsureLocal(const v8::Local<T> &val) {
                           ^
../node_modules/nan/nan.h:757:13: error: ‘node::smalloc’ has not been declared
     , node::smalloc::FreeCallback callback
             ^
../node_modules/nan/nan.h:757:35: error: expected ‘,’ or ‘...’ before ‘callback’
     , node::smalloc::FreeCallback callback
                                   ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(char*, size_t, int)’:
../node_modules/nan/nan.h:761:50: error: ‘callback’ was not declared in this scope
         v8::Isolate::GetCurrent(), data, length, callback, hint);
                                                  ^
../node_modules/nan/nan.h:761:60: error: ‘hint’ was not declared in this scope
         v8::Isolate::GetCurrent(), data, length, callback, hint);
                                                            ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(const char*, uint32_t)’:
../node_modules/nan/nan.h:768:67: error: call of overloaded ‘New(v8::Isolate*, const char*&, uint32_t&)’ is ambiguous
     return node::Buffer::New(v8::Isolate::GetCurrent(), data, size);
                                                                   ^
../node_modules/nan/nan.h:768:67: note: candidates are:
In file included from ../node_modules/nan/nan.h:25:0,
                 from ../src/binding.cpp:1:
/home/dave/.node-gyp/4.1.1/src/node_buffer.h:31:40: note: v8::MaybeLocal<v8::Object> node::Buffer::New(v8::Isolate*, v8::Local<v8::String>, node::encoding) <near match>
 NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                        ^
/home/dave/.node-gyp/4.1.1/src/node_buffer.h:31:40: note:   no known conversion for argument 3 from ‘uint32_t {aka unsigned int}’ to ‘node::encoding’
/home/dave/.node-gyp/4.1.1/src/node_buffer.h:43:40: note: v8::MaybeLocal<v8::Object> node::Buffer::New(v8::Isolate*, char*, size_t) <near match>
 NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                        ^
/home/dave/.node-gyp/4.1.1/src/node_buffer.h:43:40: note:   no known conversion for argument 2 from ‘const char*’ to ‘char*’
In file included from ../src/binding.cpp:1:0:
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(uint32_t)’:
../node_modules/nan/nan.h:772:61: error: could not convert ‘node::Buffer::New(v8::Isolate::GetCurrent(), ((size_t)size))’ from ‘v8::MaybeLocal<v8::Object>’ to ‘v8::Local<v8::Object>’
     return node::Buffer::New(v8::Isolate::GetCurrent(), size);
                                                             ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanBufferUse(char*, uint32_t)’:
../node_modules/nan/nan.h:779:12: error: ‘Use’ is not a member of ‘node::Buffer’
     return node::Buffer::Use(v8::Isolate::GetCurrent(), data, size);
            ^
../src/binding.cpp: In function ‘void dispatched_async_uv_callback(uv_async_t*)’:
../src/binding.cpp:70:35: warning: ‘void node::FatalException(const v8::TryCatch&)’ is deprecated (declared at /home/dave/.node-gyp/4.1.1/src/node.h:282): Use FatalException(isolate, ...) [-Wdeprecated-declarations]
     node::FatalException(try_catch);
                                   ^
../src/binding.cpp: In function ‘void make_callback(uv_work_t*)’:
../src/binding.cpp:245:35: warning: ‘void node::FatalException(const v8::TryCatch&)’ is deprecated (declared at /home/dave/.node-gyp/4.1.1/src/node.h:282): Use FatalException(isolate, ...) [-Wdeprecated-declarations]
     node::FatalException(try_catch);
                                   ^
../src/binding.cpp: In function ‘void ImportedCallback(const v8::FunctionCallbackInfo<v8::Value>&)’:
../src/binding.cpp:365:35: warning: ‘void node::FatalException(const v8::TryCatch&)’ is deprecated (declared at /home/dave/.node-gyp/4.1.1/src/node.h:282): Use FatalException(isolate, ...) [-Wdeprecated-declarations]
     node::FatalException(try_catch);
                                   ^
binding.target.mk:128: recipe for target 'Release/obj.target/binding/src/binding.o' failed
make: *** [Release/obj.target/binding/src/binding.o] Error 1
make: Leaving directory '/home/dave/code/jspm-react/node_modules/gulp-sass/node_modules/node-sass/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/dave/code/jspm-react/node_modules/gulp-sass/node_modules/node-sass/node_modules/pangyp/lib/build.js:272:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 3.19.0-15-generic
gyp ERR! command "/apps/node-v4.1.1-linux-x64/bin/node" "/home/dave/code/jspm-react/node_modules/gulp-sass/node_modules/node-sass/node_modules/pangyp/bin/node-gyp" "rebuild"
gyp ERR! cwd /home/dave/code/jspm-react/node_modules/gulp-sass/node_modules/node-sass
gyp ERR! node -v v4.1.1
gyp ERR! pangyp -v v2.3.2
gyp ERR! not ok 
Build failed
[email protected] /home/dave/code/jspm-react/node_modules/node-sass
[email protected] /home/dave/code/jspm-react/node_modules/gulp-sass/node_modules/node-sass

Is it really needed to include karma here?

Wouldn't it be possible to just load tests in node via system.js and run mocha directly? Why do we need karma, which was made for projects with script tag soup in index.html without proper modules?

gulp dist won't run

C:\projects\jspm-react>gulp dist
[22:23:07] Using gulpfile C:\projects\jspm-react\gulpfile.js
[22:23:07] Starting 'dist'...
[22:23:07] Starting 'delete-dist'...
[22:23:07] Finished 'delete-dist' after 1.46 ms
[22:23:07] Starting 'js'...
[22:23:07] Starting 'sass'...
[22:23:08] Finished 'dist' after 261 ms
[22:23:08] null
[22:23:08] Finished 'sass' after 301 ms
[22:23:08] Finished 'js' after 333 ms
[22:23:08] Starting 'build'...
[22:23:08] Finished 'build' after 5.7 µs
[22:23:08] Starting 'css'...
[22:23:08] Starting 'html'...
[22:23:08] Finished 'html' after 1.45 ms
[22:23:08] Starting 'js'...
[22:23:08] Finished 'js' after 5.2 ms
[22:23:08] Starting 'bundle'...
[22:23:08] Finished 'css' after 119 ms
Building the single-file sfx bundle for build/js/main.js!jsx...

err TypeError: Cannot read property 'suppressDeprecationMessages' of undefined
at Logger.deprecate (evalmachine.:8889:24)
at File.normalizeOptions (evalmachine.:8271:18)
at new File (evalmachine.:8237:22)
at TransformerPipeline.transform (evalmachine.:12107:16)
at C:\projects\jspm-react\node_modules\jspm\node_modules\systemjs-build
er\compilers\es6.js:125:31
at tryCatchReject (C:\projects\jspm-react\node_modules\jspm\node_module
s\systemjs\node_modules\es6-module-loader\dist\es6-module-loader.src.js:1183:30)

     at runContinuation1 (C:\projects\jspm-react\node_modules\jspm\node_modu

les\systemjs\node_modules\es6-module-loader\dist\es6-module-loader.src.js:1142:4
)
at Fulfilled.when (C:\projects\jspm-react\node_modules\jspm\node_module
s\systemjs\node_modules\es6-module-loader\dist\es6-module-loader.src.js:930:4)
at Pending.run (C:\projects\jspm-react\node_modules\jspm\node_modules\s
ystemjs\node_modules\es6-module-loader\dist\es6-module-loader.src.js:821:13)
at Scheduler._drain (C:\projects\jspm-react\node_modules\jspm\node_modu
les\systemjs\node_modules\es6-module-loader\dist\es6-module-loader.src.js:97:19)

     at Scheduler.drain (C:\projects\jspm-react\node_modules\jspm\node_modul

es\systemjs\node_modules\es6-module-loader\dist\es6-module-loader.src.js:62:9)
[22:23:10] 'bundle' errored after 2.22 s
[22:23:10] Error in plugin 'gulp-shell'
Message:
Command failed:
Details:
killed: false
code: 1
signal: null
stdout: Building the single-file sfx bundle for build/js/main.js!jsx...

err TypeError: Cannot read property 'suppressDeprecationMessages' of undefined
at Logger.deprecate (evalmachine.:8889:24)
at File.normalizeOptions (evalmachine.:8271:18)
at new File (evalmachine.:8237:22)
at TransformerPipeline.transform (evalmachine.:12107:16)
at C:\projects\jspm-react\node_modules\jspm\node_modules\systemjs-build
er\compilers\es6.js:125:31
at tryCatchReject (C:\projects\jspm-react\node_modules\jspm\node_module
s\systemjs\node_modules\es6-module-loader\dist\es6-module-loader.src.js:1183:30)

     at runContinuation1 (C:\projects\jspm-react\node_modules\jspm\node_modu

les\systemjs\node_modules\es6-module-loader\dist\es6-module-loader.src.js:1142:4
)
at Fulfilled.when (C:\projects\jspm-react\node_modules\jspm\node_module
s\systemjs\node_modules\es6-module-loader\dist\es6-module-loader.src.js:930:4)
at Pending.run (C:\projects\jspm-react\node_modules\jspm\node_modules\s
ystemjs\node_modules\es6-module-loader\dist\es6-module-loader.src.js:821:13)
at Scheduler._drain (C:\projects\jspm-react\node_modules\jspm\node_modu
les\systemjs\node_modules\es6-module-loader\dist\es6-module-loader.src.js:97:19)

     at Scheduler.drain (C:\projects\jspm-react\node_modules\jspm\node_modul

es\systemjs\node_modules\es6-module-loader\dist\es6-module-loader.src.js:62:9)

stderr:

Error running task sequence: { task: 'bundle',
message: 'bundle stream',
duration: 2.223091719,
hrDuration: [ 2, 223091719 ],
err:
{ [Error: Command failed: ]
killed: false,
code: 1,
signal: null,
stdout: ' Building the single-file sfx bundle for build/js/main.js!jsx.
..\n\nerr TypeError: Cannot read property 'suppressDeprecationMessages' of un
defined\n at Logger.deprecate (evalmachine.:8889:24)\n
at File.normalizeOptions (evalmachine.:8271:18)\n at new Fi
le (evalmachine.:8237:22)\n at TransformerPipeline.transform
(evalmachine.:12107:16)\n at C:\projects\jspm-react\node_m
odules\jspm\node_modules\systemjs-builder\compilers\es6.js:125:31\n
at tryCatchReject (C:\projects\jspm-react\node_modules\jspm\node_modules
systemjs\node_modules\es6-module-loader\dist\es6-module-loader.src.js:1183:3
0)\n at runContinuation1 (C:\projects\jspm-react\node_modules\jspm
node_modules\systemjs\node_modules\es6-module-loader\dist\es6-module-loader
.src.js:1142:4)\n at Fulfilled.when (C:\projects\jspm-react\node_modu
les\jspm\node_modules\systemjs\node_modules\es6-module-loader\dist\es6-mo
dule-loader.src.js:930:4)\n at Pending.run (C:\projects\jspm-react\no
de_modules\jspm\node_modules\systemjs\node_modules\es6-module-loader\dist
\es6-module-loader.src.js:821:13)\n at Scheduler._drain (C:\projects\j
spm-react\node_modules\jspm\node_modules\systemjs\node_modules\es6-module-
loader\dist\es6-module-loader.src.js:97:19)\n at Scheduler.drain (C:
projects\jspm-react\node_modules\jspm\node_modules\systemjs\node_modules
es6-module-loader\dist\es6-module-loader.src.js:62:9)\n',
stderr: '',
name: 'Error',
message: 'Command failed: ',
stack: 'Error: Command failed: \n at ChildProcess.exithandler (child_pro
cess.js:648:15)\n at ChildProcess.emit (events.js:98:17)\n at maybeClose (
child_process.js:756:16)\n at Socket. (child_process.js:969:11)\n
at Socket.emit (events.js:117:20)\n at Pipe.close (net.js:465:12)',
showStack: false,
showProperties: true,
plugin: 'gulp-shell' } }

C:\projects\jspm-react>

There is no testing in the tests

There is not actually any testing being done of the React components in the tests. It would very interesting to add this, because this is where most people get stuck.

index.html is not functioning after in production (after "gulp dist")

hi folks,

Perhaps I am missing something, but here is my problem:
after running gulp dist to go on "production mode", all javascript files are bundled ok but the index.html there are still references to jspm_packages folder and also to some of the JavaScript files as follows:

   <head>
       <link rel="stylesheet" href="jspm_packages/github/twbs/[email protected]/css/bootstrap.css"/>
       <link rel="stylesheet" href="build/css/main.css"/>
    </head>
    <body>
        <script src="jspm_packages/system.js"></script>
        <script src="config.js"></script> 
        <script>
             System.import('build/js/main.js!jsx');
        </script>
    </body>

all those references are no longer exists in dist folder, which is created in the gulp dist task.
Should I configure something to make some adjustments? maybe calling another task to create my own "production mode" html?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.