What’s new in 7.12beta3 (2023-Aug-24 12:15):
Changes in this release:
!) ethernet — changed «advertise» and «speed» arguments, and removed «half-duplex» setting under «/interface ethernet» menu;
!) sfp — convert configuration to support new link modes for SFP and QSFP type of interfaces;
*) bgp — fixed «atomic-aggregate» always set in output;
*) bgp — fixed local and remote port settings for BGP connections;
*) bgp — increase «hold-time» limit to 65000;
*) bridge — fixed fast-path forwarding with HW offloaded vlan-filtering (introduced in v7.11);
*) bridge — fixed untagged VLAN entry disable;
*) bridge — fixed vlan-filtering stability with HW and non-HW offloaded ports (introduced in v7.10);
*) bridge — improved vlan-filtering bridge stability with CAPsMAN (introduced in v7.11);
*) bth — added «Back To Home» VPN service for ARM, ARM64, and TILE devices;
*) calea — improved system stability when trying to add rules without the CALEA package;
*) console — added «transform» property for «:convert» command;
*) console — fixed scheduler «on-event» script highlighting when editing;
*) console — improved multi-argument property parsing into array;
*) console — improved stability when editing long scripts;
*) console — show full date and time in scheduler «next-run» property;
*) dhcp — fixed DHCP server and relay related response delays;
*) ethernet — added «supported» and «sfp-supported» values for «monitor» command;
*) interface — added «macvlan» interface support;
*) ipsec — fixed IPSec policy when using modp3072;
*) ipv6 — fixed IPv6 RA delay time from 5s to 500ms according to RFC;
*) ipv6 — send RA and RA deprecate messages out three times instead of just once;
*) log — improved logging for user actions;
*) lte — added at-chat support and increased wait time on modem at-chat for Dell DW5821e, DW5821e-eSIM, DW5829e and DW5829e-eSIM;
*) lte — added SINR reporting for FG621-EA modem;
*) lte — fixed Sierra modem detection for modems with vendor-specific USB descriptors;
*) lte — fixed startup race condition when SIM card is in non-default slot for LtAP mini;
*) netinstall-cli — prioritise interface option over address option;
*) ospf — fixed adding ECMP routes;
*) ospf — fixed OSPFv3 not working with NSSA areas;
*) ospf — fixed parsing of opaque LSAs used by TE;
*) ospf — fixed translated NSSA routes not showing in backbone;
*) port — add support for Huawei MS237h-517;
*) port — expose NMEA/DIAG ports for Dell DW5821e and DW5821e-eSIM;
*) quickset — fixed «LAN» interface list members if configuration does not contain bridge;
*) rip — added BFD support;
*) rip — fixed session not working in VRF;
*) route — fixed gateway after link restart;
*) route — removed deprecated «received-from» property;
*) sfp — improved interface stability for SFP and QSFP types of interfaces;
*) switch — improved switch chip stability for CCR2004-16g-2s+ devices;
*) tile — improved system stability when using queues;
*) traffic-generator — added «priority» property for «inject» command;
*) wifiwave2 — added comment property for registration-table;
*) wifiwave2 — enable changing interface MTU and L2MTU;
*) wifiwave2 — fixed malformed Interworking packet elements;
*) winbox — allow to set multiple addresses and added IPv6 support under «Interface/VETH» menu;
*) wireguard — added «wg-add-client» configuration wizard (CLI only);
*) wireguard — added «wg-export» and «wg-import» functionality (CLI only);
*) wireless — fixed malformed Interworking packet elements;
*) x86 — added support for Mellanox ConnectX-6 Dx NIC;
Other changes since v7.11:
*) bgp — fixed typos and missing spaces in log messages;
*) bridge — improved system stability;
*) certificate — allow to get and maintain Let’s Encrypt certificate in IPv6 environment;
*) certificate — fixed «subject-alt-name» duplicating itself when SCEP is used;
*) certificate — improved certificate validation logging error messages;
*) certificate — log CRL HTTP errors under the «error» logging topic;
*) chr — increased OVA default RAM amount from 160MB to 256MB;
*) console — added «:jobname» command;
*) console — added «as-string» and «as-string-value» properties for «get» command;
*) console — added «terminal/ask» command;
*) console — improved «:totime» and «:tonum» commands and added «:tonsec» command for time value manipulation;
*) console — improved stability and responsiveness;
*) console — improved stability when using «special-login»;
*) firewall — added «ein-snat» and «ein-dnat» connection NAT state matchers for filter and mangle rules;
*) ike1 — log an error when non-RSA keys are being used;
*) iot — fixed an issue where applying a script to GPIO pin caused GPIO to stop working;
*) iot — fixed behavior where GPIO output state would change on boot;
*) lte — fixed Sierra modem initialization;
*) lte — use more compact logging messages;
*) modbus — added additional security settings for Modbus TCP;
*) mpls — added option to match and set MPLS EXP with bridge and mangle rules;
*) mpls — fixed «propagate-ttl=no» setting;
*) netinstall — added option to discard branding package;
*) ospf — fixed BFD on virtual-link with configured VRF;
*) ovpn — added «tls-auth» option support for imported .ovpn profiles;
*) sfp — fixed missing «rx-power» monitor with certain modules (introduced in v7.10);
*) ssh — added support for user ed25519 public keys;
*) ssh — allow to specify key owner on import;
*) ssh — fixed SSH tunnel performance (introduced in v7.10);
*) supout — added LLDP power to supout.rif;
*) supout — fixed BFD section;
*) system — improved system stability when MD5 checksums are used;
*) wifiwave2 — list APs with a higher maximum data rate as more preferable roaming candidates;
*) winbox — allow to change port numbers for SCTP, DCCP, and UDP-LITE protocols under «IP/Firewall» menus;
Use saved searches to filter your results more quickly
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.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Describe the bug
After npx create-react-app frontend —template typescript , when you update package.json to use «typescript»: «^5.0.2», , npm install fails with this error:
Did you try recovering your dependencies?
Default installation with the only change being typescript version in package.json
Which terms did you search for in User Guide?
Environment
current version of create-react-app: 5.0.1
running from /home/juha/.npm/_npx/c67e74de0542c87c/node_modules/create-react-app
Steps to reproduce
- Run npx create-react-app frontend —template typescript
- Update package.json to use typescript: «^5.0.2»
- Run npm install
- Error appears
Expected behavior
npm install would run successfully.
Actual behavior
Reproducible demo
Default CRA using npx create-react-app frontend —template typescript
modify package.json to have «typescript»: «^5.0.2»
run npm install
The text was updated successfully, but these errors were encountered:
Workaround
CRA seems to work fine with TypeScript 5. So, if you need a temporary workaround for the error and happy to continue working with it, you can achieve that by creating a new overrides section in your package.json (if not existing already), and adding the same typescript version in dependences to it.
- Build generates a bunch of TypeError: Cannot set property mark of # which has only a getter warnings, but does not fail the build.
- Tests pass.
I am going to test this on a more substantial application as well.
Experiencing both issues ( TypeError: Cannot set property mark of # which has only a getter & the npm errors when running install)
The TypeError doesn’t keep npm run build from completing, but will prevent the application from building with Docker.
For me, the mentioned work around only suppresses the error when running npm install
I solved the TypeError by adding «fork-ts-checker-webpack-plugin»: «^6.5.3» to devDependencies, removing node_modules and lock file and reinstalling. If it doesn’t work, make sure the correct version of fork-ts-checker-webpack-plugin is installed by going to the lock file, and remove package manager cache if necessary.
The dependency declarations for react-scripts 5.0.1 did not change, but the resulting behavior certainly did. Without any actual release notes for 5.0.3, it is not at all clear what actually changed that might have caused this.
EDIT: Never mind. Deleting node_modules and reinstalling everything (without the overrides entry) caused the error to reappear. Probably something to do with caching in my IDE.
Is there some patch coming to fix this? I updated typescript to v5 and now react-scripts is failing, and we won’t put an overrides on our project, that’s a workaround not a fix
This worked for me:
Just bringing this PR to attention to hopefully bump it’s visibility and get it approved. This should resolve the issue going forward: #13071
I just used this override in package.json to make npm i work:
Describe the bug
After npx create-react-app frontend —template typescript , when you update package.json to use «typescript»: «^5.0.2», , npm install fails with this error:
Did you try recovering your dependencies?
Default installation with the only change being typescript version in package.json
Which terms did you search for in User Guide?
Environment
Steps to reproduce
- Run npx create-react-app frontend —template typescript
- Update package.json to use typescript: «^5.0.2»
- Run npm install
- Error appears
Expected behavior
npm install would run successfully.
Actual behavior
Reproducible demo
Default CRA using npx create-react-app frontend —template typescript modify package.json to have «typescript»: «^5.0.2» run npm install
Yes , its still an active issue , for me solved removing typescript , running npm i and then install again typescript.
lorenzocorallo added a commit to lorenzocorallo/TheTOLProject that referenced this issue Apr 26, 2023
MarcusFelling added a commit to microsoft/contosotraders-cloudtesting that referenced this issue Jun 29, 2023
MarcusFelling added a commit to microsoft/contosotraders-cloudtesting that referenced this issue Jun 29, 2023
On March 16, 2023, React published new docs and dropped support for the old docs. In the new docs, they no longer recommend CRA as a solution for creating React applications. It essentially means it’s dead. Instead of waiting for the fix here, I would recommend trying to find alternatives to migrate out of the CRA. You can find many articles confirming my statement.
Which is EXACTLY the problem reported by this issue ?.
If react-scripts did not have a dependency check that disallowed any 5.x version of typescript, we would all be happy,
On March 16, 2023, React published new docs and dropped support for the old docs. In the new docs, they no longer recommend CRA as a solution for creating React applications. It essentially means it’s dead. Instead of waiting for the fix here, I would recommend trying to find alternatives to migrate out of the CRA. You can find many articles confirming my statement.
CRA & react-scripts is dead, and for good reasons.
What kind of good reasons?
On March 16, 2023, React published new docs and dropped support for the old docs. In the new docs, they no longer recommend CRA as a solution for creating React applications. It essentially means it’s dead. Instead of waiting for the fix here, I would recommend trying to find alternatives to migrate out of the CRA. You can find many articles confirming my statement.
Just gave Vite a try by creating a dummy project (React + TypeScript). Got an error when I tried to npm install even though this is exactly what it told me to do.
Honestly it doesn’t seem any better than CRA for the moment, creating a sample project doesn’t work as well.
Also I stumbled on this open issue from 2021 and I don’t really like the look of this.