Comments (7)
cc/ @jasonkarns for visibility and/or 🧂
from scripty.
@searls too late. I was railing about this on Twitter when this behavior was announced (while npm7 was still in beta)
https://twitter.com/JessTelford/status/1258549958728286208
https://twitter.com/jasonkarns/status/1293736534403887106
from scripty.
I'm not likely to have time to work on this soon, but I want to note what I've found about fixing this so far.
Here's what I think options compatibility with npm 7 will require:
- Figure out how to handle implementing and testing this in both npm 6 and 7; npm 6 is still the default for LTS versions of node (v10, v12, and v14 as of this writing), so I think it makes sense to support both versions
- Code that uses
npm_package_scripty_*
(just lib/load-option.js) will need to be updated to also/instead usenpm_package_json
(per the RFC) and then parse the file from that env var to find scripty options - Update several test files (lib/load-option.test.js, test/safe/modules-test.js, test/safe/relative-path-loading.js) that specify
npm_package_scripty_*
env vars to also/instead work based onnpm_package_json
from scripty.
So, are you going to to something about this ?
from scripty.
+1
from scripty.
Seems to be an even bigger issue with yarn 2+ as currently does not have npm_package_json
available
from scripty.
This should be resolved in scripty 2.1.0 (via #105). Note that you'll want to put your scripty
config underneath a config
key, per the updated README. Feel free to comment/reopen if this is not actually fixed!
from scripty.
Related Issues (20)
- The scripty.path config is not work. HOT 2
- Bug while sharing scripts via node modules HOT 3
- Update dependency to remove vulnerability. HOT 2
- Scripts Path Not Read With Yarn 3
- PNPM Support HOT 3
- monorepo single config HOT 2
- In MAC, may be unenforceable directory, how can do before running scripts, automatically run chmod + x scripts/path/to/my/script HOT 7
- scripty ERR! It seems you may be running scripty from the command-line directly HOT 1
- pnpm build error, unknown options: 'commitizen_path', 'scripty_path', 'scripty_windowsPath' #
- Scripts fail with Node.js v >=18 HOT 3
- Revive builtIn scripts resolver HOT 2
- Batch scripts skip directories HOT 1
- Sharable scripts via a npm package HOT 3
- Default to silent mode; allow verbose option HOT 1
- multiple script locations HOT 6
- Allow directly running using "scripty <target>" HOT 8
- npm proposal for proxying "npm run"
- Script name and content is always printed HOT 3
- Issue while running scripty on windows10 HOT 7
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 scripty.