This release brings the project up to date with aframe 1.5.0, ensuring
compatibility and leveraging the latest features of aframe. Alongside
this, the README.md has been updated to provide clearer usage
instructions, enhancing the user experience. Additionally, a significant
cleanup was done by removing numerous dev dependencies, which will
necessitate replacements for future development. These changes aim to
streamline the development process while maintaining the functionality
and usability of the aframe-click-drag-component.
- Support for aframe 1.5.0 ensures compatibility with the latest
version, bringing new features and improvements to users.
- Updated README.md with clearer instructions improves the ease of use
and approachability for new users.
- Removed dev dependencies to tidy up the project structure,
highlighting a shift towards a more streamlined and focused development
process.
Upgraded to A-Frame 1.5.0 for improved VR features and compatibility,
and switched to a maintained version of the aframe-click-drag-component
to ensure ongoing support and stability.
This update addresses potential compatibility issues with newer VR
environments and provides access to the latest features and fixes from
A-Frame. By moving to a maintained version of the click-drag component,
we ensure that our application stays robust against future changes in
the A-Frame ecosystem.
compatibility
Updated the README.md to reflect changes in usage and installation for
the updated A-Frame click-drag component, ensuring compatibility with
A-Frame version 1.5.0. The installation instructions now point to a new
package name, indicating a shift in the repository and maintenance.
Adjustments include a more structured HTML example for better
readability and an update in the import paths to align with the new
package name. The entry point in package.json was also shifted from
`src/index.js` to `lib/index.js`, potentially indicating a change in the
build or distribution process to enhance library usage. These changes
aim to provide a clear, updated path for users integrating the
click-drag functionality with the latest A-Frame version, ensuring
continued support and ease of use.
Switched the repository URL in package.json from a public GitHub link to
a private Git server. This change enhances project security by moving to
a controlled, private repository and ensures that only authorized
contributors have access to the project's source code.
ownership transfer
Bumped the version to 4.0.0 to signify a major update, reflecting
potentially breaking changes or significant feature additions.
Transitioned ownership details, including author, issue tracking URLs,
and project homepage to a new maintainer, Kumi. This shift indicates a
formal handover in project stewardship, ensuring continued support and
development under new management.
Changed the 'main' field in package.json to point to 'src/index.js'
instead of 'lib/index.js'. This update aligns the entry point with the
source code to simplify the development process and ensure that the
latest features and fixes are readily accessible. The build script
remains in place for pre-publication compilation, maintaining
compatibility with environments expecting transpiled code.
This shift encourages direct use of the source module, facilitating
easier debugging and faster iteration during development.
Forked the original aframe-click-drag-component to ensure compatibility
with A-Frame 1.5.0, addressing the lack of maintenance and updates. This
version removes the call for new maintainers and clarifies the project
is a continuation of the original work. The update allows users to
maintain interactivity in 3D A-Frame scenes with current versions.
This change ensures that developers using A-Frame for VR projects can
continue to implement click and drag functionality without being
hindered by outdated dependencies or unresolved issues.
Standardized single quotes to double quotes and removed unnecessary
commas for a more consistent code style across the file. Removed unused
imports and whitespace, contributing to a cleaner and more readable
codebase. Additionally, optimized the way Quaternion and Vector3 objects
are reused, reducing the need for creating new instances, thus
potentially improving memory usage and performance slightly.
No API changes or behavior modifications were introduced, ensuring
backward compatibility.
Updated several dependencies to their newer versions to leverage recent
fixes and improvements, enhance security, and ensure compatibility with
modern environments. This includes updates to core utilities, stream
management tools, glob matching libraries, and more. Significant changes
include updates to `lodash`, `minimatch`, `source-map`, and `three`.
Ensuring these updates also involved minor adjustments for compatibility
with updated API surfaces and behavior.
These changes may improve overall performance, offer better features,
and close potential security gaps in previous versions.
Kumi
