Comparing version 0.0.1 to 0.0.2
@@ -5,3 +5,3 @@ (function webpackUniversalModuleDefinition(root, factory) { | ||
else if(typeof define === 'function' && define.amd) | ||
define([], factory); | ||
define("JDate", [], factory); | ||
else if(typeof exports === 'object') | ||
@@ -241,2 +241,3 @@ exports["JDate"] = factory(); | ||
// Export `JDate` class to global scope | ||
exports.default = JDate; | ||
exports.JDate = JDate; | ||
@@ -243,0 +244,0 @@ /* WEBPACK VAR INJECTION */}.call(exports, (function() { return this; }()))) |
@@ -187,2 +187,4 @@ // Cache original `Date` class. User may set window.Date = JDate | ||
// Export `JDate` class to global scope | ||
export default JDate; | ||
export { JDate as JDate }; | ||
{ | ||
"name": "j-date", | ||
"version": "0.0.1", | ||
"version": "0.0.2", | ||
"description": "Date class implementation in Jalali calendar", | ||
@@ -5,0 +5,0 @@ "main": "dist/index.js", |
@@ -11,3 +11,3 @@ # Date class implementation in Jalali calendar | ||
maintenance and modern development, still I'm not sure about it's possible logical bugs! I refactored | ||
[this code](https://github.com/tahajahangir/jdate) to modern an modular npm package for ease of use in modern work flow. | ||
[this code](https://github.com/tahajahangir/jdate) to a modern and modular npm package for ease of use in modern work flow. | ||
@@ -14,0 +14,0 @@ ## TO DO: |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
157593
4091