Trying to add ttypescript to webpack #41

Activity

1. harrysolovay commented on Apr 3, 2019

   

   harrysolovay

   on Apr 3, 2019

   Owner

   More actions

   @nidomiro you're pointing to the env rescript. To solve your problem, delete the following from your package.json:

   - "rescripts": [
   -   "env"
   - ]

   Then, change your .rescriptsrc.js to the following:

   module.exports = [
     'env',
     config => {
       config.modules.rules.unshift({
         test: /\.(ts|tsx)$/,
         use: [
           {
             loader: require.resolve('ts-loader'),
             options: {
               compiler: 'ttypescript'
             }
           }
         ]
       });
       return config
     }
   ]
2. harrysolovay

   closed this as completedon Apr 3, 2019
3. nidomiro commented on Apr 3, 2019

   

   nidomiro

   on Apr 3, 2019

   Last edited by nidomiro

   Author

   More actions

   @harrysolovay thanks for your reply.
   The .rescriptsrc.js is used now. :)
   Unfortunately it does not work, an produces the error:

   > BROWSER=none rescripts start
   
   Cannot read property 'rules' of undefined
   npm ERR! code ELIFECYCLE
   npm ERR! errno 1
   npm ERR! reactsandbox@0.1.0 start: `BROWSER=none rescripts start`
   npm ERR! Exit status 1
   npm ERR! 
   npm ERR! Failed at the reactsandbox@0.1.0 start script.
   npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
   
   npm ERR! A complete log of this run can be found in:
   npm ERR!     /home/niclas/.npm/_logs/2019-04-03T17_37_41_108Z-debug.log
   
   Process finished with exit code 1
   

   Maybe you can help me better if you know the Repository: https://gitlab.com/nidomiro/reactsandbox/tree/ie11
4. harrysolovay commented on Apr 4, 2019

   

   harrysolovay

   on Apr 4, 2019

   Owner

   More actions

   One thing that might help is rewriting your rule-overriding "Rescript". If you follow these guidelines, you'll avoid possible conflicts with the env Rescript. At first glance, that's what I think is causing your problem. You could also try swapping the order (place the env rescript last). Also try using the full name @rescripts/rescript-env instead of just env. If all else fails, require the env Rescript into your config:

   module.exports = [
     config => {
       config.modules.rules.unshift({
         test: /\.(ts|tsx)$/,
         use: [
           {
             loader: require.resolve('ts-loader'),
             options: {
               compiler: 'ttypescript'
             }
           }
         ]
       });
       return config
     },
     require('@rescripts/rescript-env'),
   ]

   Please let me know if these solutions don't work, and I'll get back to you with more support (hopefully it works now though!)

   Kind regards,

   Harry
5. nidomiro commented on Apr 5, 2019

   

   nidomiro

   on Apr 5, 2019

   Author

   More actions

   Thanks for your reply :)
   Your given code is not working for me.
   While trying to fix the problem I realized that CRA uses the ts-compiler only to verify the types and babel to compile to js.
   I found https://github.com/epeli/babel-plugin-ts-optchain and it fixed the root-problem of using oc without Proxy (ie11 compatibility).

   Thanks for your work and time,
   Niclas
6. harrysolovay commented on Apr 5, 2019

   

   harrysolovay

   on Apr 5, 2019

   Owner

   More actions

   Gotcha––glad to hear you were able to find a solution & thanks trying Rescripts. Please let me know if you need any more support :)
7. bretuobay commented on Aug 22, 2019

   

   bretuobay

   on Aug 22, 2019

   More actions

   For anyone running into this, I found out that the given script is wrong. This might help :)

   config => {
     config.module.rules.unshift({
       test: /\.(ts|tsx)$/,
       use: [
         {
           loader: 'ts-loader',
           options: {
             compiler: 'ttypescript'
           }
         }
       ]
     });
     return config
   },