-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Ensure style-spec is published with mapbox-gl #6586
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -116,10 +116,11 @@ | |
"sourceCache": true | ||
}, | ||
"scripts": { | ||
"build-dev": "rollup -c --environment BUILD:dev && build/run-tap --no-coverage test/build/dev.test.js", | ||
"build-dev": "rollup -c --environment BUILD:dev", | ||
"watch-dev": "rollup -c --environment BUILD:dev --watch", | ||
"build-min": "rollup -c --environment BUILD:production && build/run-tap --no-coverage test/build/min.test.js", | ||
"build-min": "rollup -c --environment BUILD:production", | ||
"build-css": "postcss -o dist/mapbox-gl.css src/css/mapbox-gl.css", | ||
"build-style-spec": "cd src/style-spec && npm run build && cd ../.. && cp -R src/style-spec/dist dist/style-spec", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Any particular reason for There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nope, just habit, will change. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Reverted to |
||
"watch-css": "postcss --watch -o dist/mapbox-gl.css src/css/mapbox-gl.css", | ||
"build-token": "node build/generate-access-token-script.js", | ||
"build-benchmarks": "BENCHMARK_VERSION=${BENCHMARK_VERSION:-\"$(git rev-parse --abbrev-ref HEAD) $(git rev-parse --short=7 HEAD)\"} rollup -c bench/rollup_config_benchmarks.js", | ||
|
@@ -141,13 +142,14 @@ | |
"test-suite": "run-s test-render test-query", | ||
"test-suite-clean": "find test/integration/{render,query}-tests -mindepth 2 -type d -not \\( -exec test -e \"{}/style.json\" \\; \\) -print | xargs -t rm -r", | ||
"test-unit": "build/run-tap --reporter classic --no-coverage test/unit", | ||
"test-build": "build/run-tap --no-coverage test/build/**/*.test.js", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Does this get run in CI? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oops, good catch -- accidentally omitted the circle.yml change |
||
"test-render": "node --max-old-space-size=2048 test/render.test.js", | ||
"test-query": "node test/query.test.js", | ||
"test-expressions": "build/run-node test/expression.test.js", | ||
"test-flow": "node build/generate-flow-typed-style-spec && flow .", | ||
"test-flow-cov": "flow-coverage-report -i 'src/**/*.js' -t html", | ||
"test-cov": "nyc --require=@mapbox/flow-remove-types/register --reporter=text-summary --reporter=lcov --cache run-s test-unit test-expressions test-query test-render", | ||
"prepublish": "in-publish && run-s build-dev build-min build-css || not-in-publish", | ||
"prepublish": "in-publish && run-s build-dev build-min build-css build-style-spec test-build || not-in-publish", | ||
"codegen": "build/run-node build/generate-style-code.js && build/run-node build/generate-struct-arrays.js" | ||
}, | ||
"files": [ | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jfirebaugh do you see any reason to do
test-build
as a separate workflow step? I thought it kinda made sense to keep it here, but 🤷♂️There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, adding it here is what I would have done too.