subeshb1 / nepali-date Goto Github PK

throws error in this line ".replace(/(?<!\)(D{1,2}|M{1,4}|Y{2,4}|d{1,3})/g, function (match) {"

possible solution: https://stackoverflow.com/questions/51568821/works-in-chrome-but-breaks-in-safari-invalid-regular-expression-invalid-group

🚨 The automated release from the master branch failed. 🚨

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

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 fix 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 are 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 for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization 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 📦🚀

Ability to parse date based on the standard date formats

Your Releases are too complex!

I am getting the error as title suggests. When I want to convert 2034/02/24 A.D to B.S.

Provide an API to format according to the provided string format

When I am passing a JS Date object as a constructor to NepaliDate, the stored Js date, in the instance, is 1 day behind the original JS date object. This is an example of the problem.

Original Date:  2021-06-08T18:15:00.000Z
Nepali Instance:  NepaliDate {
  [Symbol(Year)]: 2078,
  [Symbol(MonthIndex)]: 1,
  [Symbol(Date)]: 25,
  [Symbol(Day)]: 2,
  [Symbol(JsDate)]: 2021-06-07T18:30:00.000Z
}
Formatted Original:  2021-06-09
Formatted Nepali Date:  2021-06-08

The format is done using Intl.DateTimeFormat.

let formatted = new Intl.DateTimeFormat('en-GB', {timeZone: process.env.TZ, month: '2-digit', day: "2-digit", year: "numeric"}).format(d);

Where process.env.TZ = 'Asia/Kathmandu'

Example:

new NepaliDate('२०७७/०३/१४')

🚨 The automated release from the master branch failed. 🚨

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

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 fix 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 are 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.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://[secure]@github.com/subeshb1/Nepali-Date.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

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 can benefit from your bug fixes and new features again.

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 fix 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 are 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.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://[secure]@github.com/subeshb1/Nepali-Date.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨

Your semantic-release bot 📦🚀

is't it supposed to print the Nepali date (2077/03/11) of input new NepaliDate(new Date(2020, 06, 25)) instead I am getting (2077/03/10) neither I am getting expected output of new NepaliDate() which is current date or am I missing something?

Problem Statement

There are vulnerable packages being used in this project, we need to fix them

Acceptance criteria

• Identify whether the packages are required or not.
• Eliminate the package or update them to safe version.

It is giving the wrong day of the week .

let a = new NepaliDate(2077,05,08);

a.format('ddd DD, MMMM YYYY', 'np')
// "बिहिबार ०८, आश्विन २०७७" <-- output

// "सोमबार ०८, भाद्र २०७७" <-- Actual Date in Nepali

When parsing invalid date 2020/20/20 it gives 20/08/2021.

The value should be the same when the string is sent to the constructor.

The reason, this bug exists is because it uses the same logic as number constructor.

Acceptance Criteria
The string value should be parsed as it is or not parsed at all.

The format ddd and dddd should both give Full week day

Problem Statement

The read me doesn't provide much information currently. We need to update it so that it provides the information listed in acceptance criteria.

Acceptance Criteria

• Installation method
• NPM package version in top
• Basic Usage documentaion
• Contributing guide

Travis.org has reached its End of Life. Migrate the CI/CD to github actions