You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current README instructions for setting up a Hardhat project recommend using a generic command to install Hardhat, which by default installs the latest version. This can lead to compatibility issues for users following tutorials designed for earlier versions, especially with significant changes like the "ignition/modules" structure introduced in newer versions.
The README should guide users to install a version of Hardhat that corresponds with the tutorial or documentation they are following, to prevent potential confusion and ensure compatibility.
Current Behavior:
The README instructs users to run npm install --save-dev hardhat without specifying a version, leading to the installation of the latest Hardhat version.
Suggested Update:
I recommend updating the README to include an optional step where users are instructed on how to install a specific version of Hardhat. For instance, it could suggest using the command npm install --save-dev [email protected], where 2.17.1 is the version number that matches the user's tutorial or project requirements. This minor adjustment can significantly enhance the user experience by ensuring compatibility and reducing confusion.
Steps to Reproduce:
Follow the initial setup instructions in the README to create a new Hardhat project.
Notice the lack of version specification in the npm install --save-dev hardhat command.
Upon installation, the latest version of Hardhat is installed, which may not be compatible with tutorial or project setups, particularly those not updated for the latest Hardhat features like "ignition/modules".
Context:
This issue arose when setting up a new Hardhat project intended to follow a specific tutorial. The tutorial assumed an earlier version of Hardhat, and the discrepancy led to confusion and compatibility problems due to the newer version's different deployment methodology.
Including a step to specify the version during Hardhat installation could greatly assist users in aligning their development environment with their educational resources or project specifications, enhancing the overall setup experience.
The text was updated successfully, but these errors were encountered:
juanc004
added a commit
to juanc004/Learning-Projects
that referenced
this issue
Mar 20, 2024
…ility
Updated README installation instructions to explicitly recommend Hardhat version 2.17.1, aligning with the requirements and ensuring full compatibility with the tutorial content addressed in Issue 0xmetaschool#442.
juanc004
changed the title
Clarification Needed on Hardhat Version Installation in 'Setting Up Environment' Lesson of 'Writing Your First Hello World Contract in Solidity' Tutorial
Simplify Hardhat Version Guidance for 'Writing Your First Hello World Contract in Solidity'
Mar 20, 2024
Description
The current README instructions for setting up a Hardhat project recommend using a generic command to install Hardhat, which by default installs the latest version. This can lead to compatibility issues for users following tutorials designed for earlier versions, especially with significant changes like the "ignition/modules" structure introduced in newer versions.
Link to the Current Instructions:
Setting up the environment for Hardhat
Expected Behavior:
The README should guide users to install a version of Hardhat that corresponds with the tutorial or documentation they are following, to prevent potential confusion and ensure compatibility.
Current Behavior:
The README instructs users to run
npm install --save-dev hardhat
without specifying a version, leading to the installation of the latest Hardhat version.Suggested Update:
I recommend updating the README to include an optional step where users are instructed on how to install a specific version of Hardhat. For instance, it could suggest using the command
npm install --save-dev [email protected]
, where2.17.1
is the version number that matches the user's tutorial or project requirements. This minor adjustment can significantly enhance the user experience by ensuring compatibility and reducing confusion.Steps to Reproduce:
npm install --save-dev hardhat
command.Context:
This issue arose when setting up a new Hardhat project intended to follow a specific tutorial. The tutorial assumed an earlier version of Hardhat, and the discrepancy led to confusion and compatibility problems due to the newer version's different deployment methodology.
Including a step to specify the version during Hardhat installation could greatly assist users in aligning their development environment with their educational resources or project specifications, enhancing the overall setup experience.
The text was updated successfully, but these errors were encountered: