Comments (5)
I’m still not sure why realpath
is required. I haven’t felt the need to symlink test/run
anywhere yet…
from faucet-pipeline-core.
I've become profoundly uncomfortable not ensuring absolute paths in cases like this:
https://github.com/faucet-pipeline/faucet-pipeline-js/blob/99c67e5dc3dcb82caf7d3245b4d7560417f8df25/test/cli/run#L5-L6
Is that excessively paranoid?
from faucet-pipeline-core.
I believe it is.
Let’s assume we omit the call to realpath
. In order for that to cause problems, someone would have to first symlink the script somewhere and then run it manually (npm test
would still run it at the correct path). I believe that a failing script is the appropriate response to that scenario.
If someone were to actually do that, what problems would arise? Loading cli-harness.sh would fail and the script would abort with a helpful error message. If someone were to fix that error by fixing the path, the next begin
would fail instead, again with a helpful error message.
I don’t think I’d do anything to prevent those errors, I’d much rather ensure that npm i && npm t
works on a clean clone.
from faucet-pipeline-core.
Oh, as a side note: I think I’d also symlink cli-harness.sh into the directories where it’s loaded in order to present a simpler environment to the test scripts.
from faucet-pipeline-core.
Done: faucet-pipeline/faucet-pipeline-js@9c80dbb (with similar commits in faucet-core, faucet-sass, faucet-static, faucet-images and nite-owl)
from faucet-pipeline-core.
Related Issues (20)
- Action required: Greenkeeper could not be activated 🚨 HOT 1
- Replace live-server with five-server?
- More customization for the manifest output HOT 1
- presets for common use cases
- `resolveModulePath` fails on legacy Node HOT 1
- Source map Support HOT 3
- Version 10 of node.js has been released HOT 1
- An in-range update of browserslist is breaking the build 🚨 HOT 2
- drop Node 6 compatibility after 04/2019 HOT 1
- Config File Details HOT 1
- simplify plugin registration HOT 20
- replace Travis CI HOT 2
- An in-range update of browserslist is breaking the build 🚨 HOT 1
- An in-range update of browserslist is breaking the build 🚨 HOT 2
- An in-range update of eslint-config-fnd is breaking the build 🚨 HOT 1
- Catch ENOSPC when watching, give hint, then crash HOT 1
- ESM compatibility HOT 1
- Missing manifest file on first run HOT 3
- `require.resolve` doesn't work for folders in `node_modules` HOT 2
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 faucet-pipeline-core.