I'm using aldeed:autoform#5. I also want to use yogiben's autoform-file, but I had trouble getting that to work with autoform#5 so I've used a fork by abdj:autoform-file.
Now I want to use yogiben:admin. According to the discussion on github and the latest master (https://github.com/yogiben/meteor-admin/blob/master/package.js), yogiben:admin#1.1.0 uses aldeed:autoform#4.2.2 || 5.0.0.
So why do I get this error?
C:\Webdev\koolaid>meteor add yogiben:admin#1.1.0
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint aldeed:autoform#4.2.2 is not satisfied by aldeed:autoform 5.1.2.
Constraints on package "aldeed:autoform":
* aldeed:autoform#5.0.2 <- abdj:autoform-file 0.2.0
* aldeed:autoform#4.2.2 <- yogiben:admin 1.1.0
Looks to me like Meteor is somehow picking up the wrong version from github? BTW I'm using Meteor WindowsPREVIEW#0.3.0.
How do I get all these packages to play nice together?
Related
Here is a link to my package.
So after updating my Swift Package and its version tag,
I am getting the following errors when I try to update the package in my project that consumes the package.
Missing package product 'MyPackage1'
ā¯•Package resolution errors must be fixed before building
https://github.com/ElevatedUnderdogs/PackageTest2.git
has no Package.swift manifest for version 1.0.1
1.0.0 is the original. 1.0.1 is my updated version.
Does this mean I need to create a new Package.swift for every single version? I don't even see a place in the Package.swift where I can signify the current version.
Things I've tried:
reseting the package cache in the consuming project.
"updating to latest package versions"
Deleting the Swift Package, and then trying to add it again. Before adding it completes, I get: "MyProject.git has no Package.swift manifest for version 1.0.1.
Package.swift is in the root directory.
In my case, the tag was updated on an incorrect remote branch which wasn't merged to yet, so the tag's corresponding commit didn't have the Package.swift file. It is a good practice to check the commit hash of the version you are trying to access to verify that it has the correct code.
I'm having a problem with Meteor, after upgrading to v1.11.
Apparently is a known issue. Do you have a workaround for this message?
=> Started proxy.
=> Errors prevented startup:
While selecting package versions:
error: Conflict: Constraint email#1.2.3 is not satisfied by email 2.0.0.
Constraints on package "email":
* email#~2.0.0 <- top level
* email#1.2.3 <- vulcan:lib 1.16.0
* email#2.0.0 <- accounts-password 1.6.2
* email#1.2.3 <- vulcan:accounts 1.16.0 <- clearbase:admin 0.1.0
=> Your application has errors. Waiting for file change.
I've tried updating the dependencies with meteor update, then manually using packagecheck but still same issue. Also tried the suggestions on the meteor release post.
This error is solved updating to meteor v1.11.1
Plus you need to add ! at the end of the dependency on packages
# .meteor/packages
email#~2.0.0!
I have a project that I plan on developing in modules, the final application will be any number of the modules built together based on a configuration. I have a swift package that has all of my common code it it, we can call that the platform package. I then went to create my first feature, this went just fine however when I created the wrapper application to pull in each feature, I got this error from SPM in xcode11:
package 'Platform' is required using a revision-based requirement and it depends on local package
'Feature1', which is not supported.
Looking at the code base for SPM here (line 72)
https://github.com/apple/swift-package-manager/blob/master/Sources/PackageGraph/DependencyResolver.swift
It looks like this is something that is just not supported, the mixing of local and remote dependencies? Is this a limitation of SPM / should I be trying to use another tool for this type of app architecture?
In my case, I was trying to add a package, which I was developing, and its Package.swift contained dependencies of the form:
dependencies: [
.package(path: "../PackageName"),
// etc
Changing the references to specific repos solved the problem:
dependencies: [
.package(path: "http://github.com/..."),
// etc
I am trying to add the autoform package to my meteor project. After running "meteor add aldeed:autoform" and adding the package - I am encountering the following errors:
Cannot find module 'mongo-object',
Cannot read property 'AutoForm' of undefined,
Uncaught ReferenceError: meteorInstall is not defined
I didn't even try to use the package. Just adding the package caused the errors. I am using Meteor 1.4.4.1
Any idea why this happens ? I followed the instruction in the autoform github repo.
The installation for autoform 6 says the following:
$ meteor add aldeed:autoform
$ npm i --save simpl-schema
Then you need (in v. >=6.0.0) to enable the use of autoform entries in SimpleSchema definitions. This is just required once, e.g. in your startup scripts:
import SimpleSchema from 'simpl-schema';
SimpleSchema.extendOptions(['autoform']);
What is not 100% clear to most people, switching to af6
you need to remove the old aldeed:simple-schema package from the meteor packages
you need to switch from the deprecated collection2 to collection2-core
you need to be aware of the change log, which indicates deprecated method and method name changes.
If you concern all of these changes it should run really fine again.
Update March 2018: collection2-core is now merged back to aldeed:collection2 so use the latest version of this package.
I'm new to Purescript and am following the tutorial for installation. Purescript itself is working and I can start the CLI using pulp psci, but installing purescript-list runs into trouble.
Having entered the command bower install purescript-lists --save, I get a long list of package names, but when it gets to purescript-eff and purescript-prelude I run into some version conflicts:
bower purescript-eff#^2.0.0 cached https://github.com/purescript/purescript-eff.git#2.0.0
bower purescript-eff#^2.0.0 validate 2.0.0 against https://github.com/purescript/purescript-eff.git#^2.0.0
Unable to find a suitable version for purescript-eff, please choose one by typing one of the numbers below:
1) purescript-eff#^1.0.0 which resolved to 1.0.0 and is required by purescript-console#1.0.0
2) purescript-eff#^2.0.0 which resolved to 2.0.0 and is required by purescript-st#2.0.0
Prefix the choice with ! to persist it to bower.json
? Answer
A similar message is shown for purescript-prelude. No matter which options I choose, both pulp build and pulp run fail with:
$ pulp build
* Building project in /Developer/purescript/training1
Error found:
in module PSCI.Support
at /Developer/purescript/training1/bower_components/purescript-psci-support/src/PSCI/Support.purs line 10, column 34 - line 10, column 53
Cannot import value unsafeInterleaveEff from module Control.Monad.Eff.Unsafe
It either does not exist or the module does not export it.
See https://github.com/purescript/purescript/wiki/Error-Code-UnknownImport for more information,
or to contribute content related to this error.
Compiling PSCI.Support
* ERROR: Subcommand terminated with exit code 1
What have I missed here?
Thanks
Chris W
If you are using psc version 0.10.* you should go with prelude, lists and eff v2*.
If you are using psc version 0.9.* you should go with prelude, lists and eff v1*.
If you are using psc 0.10.* you might want to update pulp to version 9.1.0
The problem occurs due to breaking changes between psc 0.9 and 0.10 and the relevant libraries. by writing bower install purescript-lists --save you are asking bower for the latest dependencies which conflict with the dependency versions specified in your bower.json.