Comments (4)
I should add that my node version is v8.11.1
.
from sequencetubemap.
This patch fixed the issue (I really don't know why, but it works):
diff --git a/frontend/gulpfile.js b/frontend/gulpfile.js
index c4c9ca8..6629fed 100644
--- a/frontend/gulpfile.js
+++ b/frontend/gulpfile.js
@@ -43,13 +43,13 @@ gulp.task('scripts', () => {
})
.bundle()
.pipe(source(entry.substr(entry.lastIndexOf('/') + 1)))
+ .pipe(buffer())
.pipe(rename({
extname: '.bundle.js',
}))
.pipe($.plumber())
// .pipe($.sourcemaps.init())
// .pipe($.babel())
- .pipe(buffer())
.pipe($.sourcemaps.init({ loadMaps: true }))
.pipe($.sourcemaps.write('.'))
.pipe(gulp.dest('.tmp/scripts'))
from sequencetubemap.
Hm. It works for me on on Linux on Node 6.5.0:
[anovak@courtyard frontend]$ git checkout upstream/master
Note: checking out 'upstream/master'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b <new-branch-name>
HEAD is now at 8662ed1 make compatible with vg version v1.7.0-103-gf87f178
[anovak@courtyard frontend]$ rm -Rf dist
[anovak@courtyard frontend]$ node_modules/gulp/bin/gulp.js
[11:27:39] Using gulpfile ~/build/sequenceTubeMap/frontend/gulpfile.js
[11:27:39] Starting 'default'...
[11:27:39] Starting 'clean'...
[11:27:39] Starting 'wiredep'...
[11:27:39] Finished 'wiredep' after 18 ms
[11:27:39] Finished 'clean' after 123 ms
[11:27:39] Starting 'lint'...
[11:27:39] Starting 'styles'...
[11:27:40] Starting 'scripts'...
[11:27:40] Starting 'images'...
[11:27:40] Starting 'fonts'...
[11:27:40] Starting 'extras'...
[11:27:40] Starting 'copyStuff'...
[11:27:40] Finished 'copyStuff' after 2.65 ms
[11:27:45] Finished 'lint' after 5.88 s
[11:27:45] Finished 'images' after 5.03 s
[11:27:45] Finished 'styles' after 5.64 s
[11:27:51] Finished 'extras' after 11 s
[11:27:51] Finished 'fonts' after 11 s
[11:27:51] Finished 'scripts' after 11 s
[11:27:51] Starting 'html'...
[11:27:57] Finished 'html' after 5.91 s
[11:27:57] Starting 'build'...
[11:27:57] build all files 251.7 kB (gzipped)
[11:27:57] Finished 'build' after 186 ms
[11:27:57] Finished 'default' after 18 s
[anovak@courtyard frontend]$ ls dist
apple-touch-icon.png examples.html favicon.ico fonts images index.html robots.txt scripts styles
But for another person in our lab on Mac we see the problem you are describing, on Node 7.0.0. Your patch seems to solve it there as well.
How did you decide to move that particular line there?
from sequencetubemap.
I have zero knowledge about gulp. So, I don't know why it exactly fixes the issue. :) In fact, I used gulp-debug
to find the problematic task and line in gulpfile.js
. Then, searched for some sample code to re-write task scripts
to "browserify" main.js
and write main.bundle.js
. The sample code worked. Then, I compared it with the original scripts
task and figured it out the only effective difference is the order of this line.
from sequencetubemap.
Related Issues (20)
- Reads can become oddly wide
- Absolute path to BED is used in link to view instead of relative path
- Curved reads/paths stay highlighted after mouse over
- Allow eliding node sequences when reads are present HOT 8
- Good wrapper script and documentation for how to inspect a list of variants
- Better handling of the case where vg is not installed
- Document which variant is meant to go with which Lancet example
- First coordinate on the coordinate bar can start further left than I can pan HOT 1
- Reads aren't clickable within nodes
- Reads from different samples interleave oddly when skipping nodes HOT 1
- Configure server to have Lancet BED URL as a top-level option alongside custom HOT 4
- Deploy tube map and publish Lancet November examples somewhere so the paper can use them
- You can hit the max zoom out in X without being able to see everything in Y HOT 1
- "Path to graph file not allowed" error when loading a link (or config data source) to a URL bed region HOT 2
- Manual pre-deployment testing
- Visualizing a graph from short sequences HOT 1
- Axis is too prone to breaks when the graph is tiny nodes
- Graph can be entirely out of the image bounds in a downloaded image
- Off by 1 error on end position bounds check HOT 1
- How to interpret variation graphs in SequenceTubeMap
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sequencetubemap.