Comments (12)
Yup, managed to accept both invitations
from node-ipc.
@AaronDewes There's a workaround by using the NPM CLI package aliases feature that I recently added above:
Q: I want to import using the original package name
NPM CLI v6.9.0 and Yarn v0.24.3 support package aliases, which allows transparent re-mapping of package names. In
package.json
:"dependencies": { "node-ipc": "npm@achrinza/node-ipc@9" }Replace the trailing
9
with the appropriate@achrinza/node-ipc
version accordingly.
Q: I want to use the DefinitelyTyped type definitions
Follow the steps in "Q: I want to import using the original package name" above and install the type definitions:
npm install --save-dev @types/node-ipc
The rationale is that the DefinitelyTyped typedef may not be stable since they map to the same semver major (e.g. @types/node-ipc@10
is for node-ipc@10
), which means breaking changes is allowed within semver major. This means that keeping up-to-date with the upstream typedef may be difficult.
By using this workaround, we would keep the familiar DefinitelyTyped contract in place.
It's a different approach to the same problem.
from node-ipc.
Thanks, I've made the changes.
from node-ipc.
@achrinza Would you be interested in collaborating on this at @node-ipc? I'm happy to give you access both there and on the npm org.
But I'm also planning to add new changes & improvements over upstream, like porting it to promises instead of callback functions, in a separate branch (probably as a separate package).
I already published v11 on @node-ipc/node-ipc
and v9 on @node-ipc/compat
and forked some dependencies.
from node-ipc.
Hi @AaronDewes,
Would you be interested in collaborating on this at https://github.com/node-ipc?
Sure thing; I'm open to working on @node-ipc
But I'm also planning to add new changes & improvements over upstream, like porting it to promises instead of callback functions, in a separate branch (probably as a separate package).
Sounds great!
from node-ipc.
I've just invited you to both the GitHub and npm org, please let me know if you got access to both.
from node-ipc.
@achrinza Not sure if you'd count it as new feature, but adding a .d.ts file to this repo would be great, because @types/node-ipc won't work with this repo.
from node-ipc.
Some feedback regarding your info about @node-ipc/node-ipc
Bundled snapshot of DefinitelyTyped
Actually, it's written in/ported to TypeScript, so the Type definitions are not a snapshot of DefinitelyTyped.
For the versions, v10 is not published to the npm registry, so please replace it with this:
v9 (via @node-ipc/compat
), v10 (via v11), v11.
from node-ipc.
"dependencies": {
"node-ipc": "npm@achrinza/node-ipc@9"
}
should be
"dependencies": {
"node-ipc": "npm:@achrinza/node-ipc@9"
}
from node-ipc.
@lukas-mertens Thanks for catching that! I've updated all the package aliases in the FAQ.
from node-ipc.
Yup, managed to accept both invitations
is this still valid? cause I see you are now working on the original repo no?
from node-ipc.
Hi @maa105, I've not contirbuted and do have push rights to the original repo, nor do I have any push nor publish rights for the original package on NPM registry.
Between @achrinza/node-ipc
and @node-ipc/node-ipc
, I support both projects. Both projects don't really require much upkeep from me, hence most changes I make to them (if any) is just for maintenance. Though @node-ipc/node-ipc
is ultimately @/AaronDewes' project, so any major updates should be from, or approved by him.
See "Q: How does this differ from @node-ipc/node-ipc?" above for more info on why the forks are managed separately.
from node-ipc.
Related Issues (20)
- Deprecation of `v10.1.3`
- Automated scanning of dependency tree for blocklisted maintainers HOT 2
- Flaky v9 macOS and Windows tests
- Deprecation of `v10.1.4`
- @vue/cli-shared-utils dependency install breaks on npm / yarn install when using non-lts versions of node HOT 5
- Support Node.js v18 HOT 2
- Issue with Version 9.2.4 on Node.js 18 HOT 3
- Support Node.js v19 HOT 2
- TypeError: Cannot read properties of undefined (reading 'log')
- Saw all your work in the middle of things an am appreciative of your efforts. HOT 3
- Support Node.js v20 HOT 4
- please support node: 'v20.4.0', npm: '9.7.2'
- Unsupported engine for node 18
- Disconnect right after emit will eat the emit
- Support Node.js v21
- Deprecation of `v10.1.5`, `v10.1.6`, `v10.1.7`, `v10.1.8`, `v10.1.9`
- Node 20.10.0 : error @achrinza/[email protected]: The engine "node" is incompatible with this module. HOT 1
- can you support latest version of node?
- Node 22.0.0 : error @achrinza/[email protected]: The engine "node" is incompatible with this module. HOT 5
- @achrinza/[email protected]: The engine "node" is incompatible with this module. Expected version "8 || 10 || 12 || 14 || 16 || 17". Got "20.12.1" HOT 1
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 node-ipc.