Proposal: Release compatible packages in @feathers(-release) scope

[j2L4e]

When Auk was out, there was a lot of confusion about which modules and which versions work together. Also it remains unclear from the package names if they are officially supported or 3rd party.
With Buzzard on the horizon the same thing's going to happen all over again, my proposal is the following:

Release everything that is auk under @feathers-auk (or @feathers-buzzard resp.) scope, so people can be sure that what they import actually works together.

Actually the package itself doesn't need to be released under that scope, but we could build packages that only include a package.json that pulls in the actual package:

// @feathers-buzzard/feathers package.json
"dependencies" : {
  "feathers": "^3.0.0"
}

// @feathers-auk/feathers package.json
"dependencies" : {
  "feathers": "^2.0.0"
}

I know feathers uses greenkeeper and I also came across #462 . I'm not sure what both are capable of and have not yet thought about a technical solution, but it doesn't seem to be too complicated.

Edit: Also I vote for "Cockatoo" being the version after buzzard

[daffl]

We have been talking before about moving all official (and maybe just core) packages into the @feathers namespace. A new release might be a good time for that.

Release specific namespaces would add the overhead of having to re-release packages that didn't need to be changed. For example, the database adapters won't have to be changed at all for the next release.

One thing I'd definitely like to implement is for plugins to do a version check against app.version and throw an error if they are not compatible. So for example feathers-rest@2.0 would throw an error for any non feathers@^3.0.0 app.

[kfern]

Sounds good 👍

[eddyystop]

I like the version check idea.

[j2L4e]

This seems feasible

// feathers (i.e. make it a function on the app instance)
const semver = require('semver')
function assertVersion(version) {
 if (!semver.satisfies(app.version, version)) {
    throw `feathers core version ${app.version} doesn't satisfy ${needed}`
  }
}

// plugin:
neededCore = '^2.1.5 || 13.3.7';
app.assertVersion(neededCoreVersion);

[marshallswain]

One thing I'd definitely like to implement is for plugins to do a version check against app.version and throw an error if they are not compatible. So for example feathers-rest@2.0 would throw an error for any non feathers@^3.0.0 app.

Yes!

[wobsoriano]

Hi guys! How can I do feathers generate service in my old feathers app when I installed the new version? Thank you.

[eddyystop]

The new generator is not compatible with modules created by the old generators. The service generator, like all the generators, writes little code. I'd just copy the modules from an old service and modify by hand.

…

On Tue, Jul 18, 2017 at 2:09 AM, Robert Anthonie ***@***.***> wrote: Hi guys! How can I do feathers generate service in my old feathers app when I installed the new version? Thank you. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#623 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABezn0RX4PtehvPfLe6NilWBJCDKA7kAks5sPEwTgaJpZM4OZBW-> .

[daffl]

Although we didn't implement the per-release organization, all core modules for the v3 pre-release have been moved to the @feathersjs scope. Upgrade instructions for beta testing can be found at https://gist.github.com/daffl/e718f93acc7bfe32fd1e5aed0f8e7827

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue with a link to this issue for related bugs.