exist-db / gulp-exist Goto Github PK

There was no new version released after merging #13 and a successful CI run. It didn't seem to see the fix and breaking commits.

semantic-release ERR! pre Failed to determine new version.
semantic-release ERR! pre ENOCHANGE There are no relevant changes, so no new version is released.

I've updated semantic-release to the latest version and it released a patch version. So I guess the commits from the merge were just skipped.

any ideas maybe @line-o? make a breaking dummy commit?

install or installPackage that can be used in .pipe()

Prerequisite

• eXist-db/node-exist#129 is merged into node-exist

Example

const { src } = require('gulp')
const { createClient } = require('@existdb/gulp-exist')
const existClient = createClient()

function install () {
  return src('my-app.xar').pipe(existClient.install())
}
exports.install = install

Ci is slow today, reminder to audit fix package-lock.json

@line-o I was thinking of putting the eXist communication stuff into a separate npm package and have gulp-exist use that. Now I saw you made such a package with node-exist a couple of days ago. Did you have something similar in mind? If so I might ditch my plan and just start maintaining a branch using your library as a backend. Any thoughts?

Gulp for changed the preferred syntax for its gulpfiles. Adopt the examples in line with what happens in the gulp docs to go with the times.

Now that the PR #1 got merged 🎉 , do you know when you will be able to release it to npm?
Just so, that a project using the fork can point to npm again.

the ci/setup.ps1 script needs updating for exist 5.0.0. The final RC that works is RC4. I have no windows around to work on this, we could also consider adding a windows build to the travis matrix, as we have more parallel builds there.

Or switch to azure pipelines, or ….

this repo should publish to npm as @existdb/gulp-exist

I saw that you are now using travis CI and semantic-release - awesome!
Why don't use standard JS as well?
It keeps code in such a good shape and covers so much ground that there is no room and no need for formatting discussions.

Hello, based on the tutorial from https://github.com/cceh/papyri
at the command "gulp deploy-local"
gulp generates the files and folders as collections in eXist
instead of saving it in apps/
Any suggestions for a solution?

eXist Version is 2.2

Defining mime types in the gulpfile like this

const exist = require('@existdb/gulp-exist');

exist.defineMimeTypes({
    'application/xml': ['odd']
});

throws an error:

Error: Attempt to change mapping for "odd" extension from "application/xml" to "application/xml".    
Pass `force=true` to allow this, otherwise remove "odd" from the list of  
 extensions for "application/xml".  
[echo]     at Mime.define

So I followed the advice in the error, went through the relevant mimetype function in module mime to check if this is really supported and added the force=true flag like this

exist.defineMimeTypes({
    'application/xml': ['odd']
}, true);

but without any effect.
In fact, whatever I add or write within defineMimeTypes will result in said error.

Never experienced that error before.
Installed modules:

• @existdb/gulp-exist 3.0.0
• mime 2.4.4
• node v10.0.0
• npm 6.9.0
• gulp 3.9.1 (CLI 2.2.0)

Should this be moved to exist-db.org here on GitHub?

There should be a bit more introductory text for those not being so familiar with gulp and npm.

• how to install it
• how to update it

It would be great if we can keep system config params in one place. These are:

• application name (used to name the .xar file)
• version
• authors
• license
• description
• ?

I actually have no strong preference of where to put it - it would be just more convenient to feed the config within the gulpfile with these params and to also token-substitute them in expath.xml and repo.xml

As some commands have changed and gulp v4 is now the standard we should change the documentation or at least have an example in the wiki.

since the travis.org api has changed we should manually migrate this repo to travis.com by sending an email to [email protected] more info

Since there are secret env variable for publishing to npm, @olvidalo would need to do this.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀